-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Context for remote host management #647
Comments
At least |
Initial trials with
|
Would be great if all modules that interact with docker also supported contexts, including default one. |
#1039 adds a |
SUMMARY
Since Docker v18.09+ it is possible to use the same
docker
CLI on a Controller Node to get access to remote Managed Nodes. This is generally achieved initially by usingdocker context create ...
.This command is capable enough to work with Docker Swarm, Kubernetes for Orchestration as well for standalone remote nodes over TCP (with / without TLS), as well as SSH.
Thorough Documentation can be found on Docker Docs: Docker Context.
The tool also provides facilities or exporting / importing these created contexts as well as controlling the Docker Containers on Remote nodes.
ISSUE TYPE
COMPONENT NAME
community.docker.docker_context
ADDITIONAL INFORMATION
This may be an example module called
docker_context
:There are certainly benefits where at least from the CLI, the following examples can perform tasks, which are performed locally, also on a remote machine
# list running docker containers on `my-host-1` docker --context=ctx-my-host-1 ps -a
In conjuction with
docker compose
one can deploy a compose application without needing to copy a compose file to the remote machine# executing in the same directory as `docker-compose.yml` docker --context=ctx-my-host-1 compose up -d
A well written Docker Post for deploying on Remote Docker Host with docker compose
The text was updated successfully, but these errors were encountered: