You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- You are looking for a way to pull and recreate your docker image after CI/CD completes.
9
9
- You want to avoid polling the container registry on an interval.
10
10
- You want to avoid setting up SSH from the pipeline into your server.
11
+
- You want to keep the ability to maintain your containers outside of CI/CD events.
11
12
12
13
## Install
13
14
@@ -49,7 +50,7 @@ services:
49
50
50
51
- Docker Socket: Mount host docker socket into the container to allow the container to execute docker commands as the host user. See security considerations below.
51
52
- Compose File (when using the compose endpoints): Crucially mount the docker-compose.yml file exactly at the same absolute path inside the container as outside on the host machine. Docker tracks the compose environment with the labels `com.docker.compose.project.config_files` and `com.docker.compose.project.working_dir`. Interacting with existing containers requires the same compose location otherwise docker will treat this as a separate compose file.
52
-
-Compose Context: If your compose project depends on additional files like env files defined in `env_file` key, make sure the container has the same context by mounting additional folders to the same location.
53
+
-Docker Context: If your project depends on additional files like env files defined in `env_file` key, make sure the container has the same context by mounting additional folders to the same location.
53
54
- If needed for authentication, mount the docker config.json file into the container at `/root/.docker/config.json`.
0 commit comments