Conclusionĭocker contexts are useful when you need to deploy containers in multiple independent environments. You can inspect a context’s meta.json file from the CLI with docker context inspect my-context. If you’re making bulk updates, you could edit the meta.json files to directly manipulate your contexts. This accepts the same flags as docker context create. If you need to edit a context, use the docker context update command. Symlinking the folder to a network share might also be an option depending on your requirements. You could use an Rsync transfer or a Git repository to simplify regular updates. If you want to synchronize context configuration, you can back up the contexts folder to move it to another machine. The default context inherits the settings from your Docker daemon configuration. Only created contexts have files stored on-disk. Inside, you’ll find a meta.json file that describes the context. Each context gets its own folder named with a unique hash. You’ll find your contexts in the contexts subdirectory. Synchronizing Contexts between MachinesĬontext files are stored in your Docker CLI’s configuration directory. It’s not possible to delete the default context. To delete a context, run docker context rm, supplying the context name. The active context is highlighted with an asterisk. This command lists all the contexts available in your CLI configuration. You can inspect the active context by running docker context ls. This variable forces Docker to use a particular daemon endpoint instead of the one provided by the context. Using the DOCKER_HOST environment variable will override the active context, too.

Local kubernetes context docker on mac