The way the build script is executing on the build container is by starting the container with the script as ps1, as soon as the script is done, the container exists.
Follow the same flow the kubernetes executor, where the build container is started in detached mode and the build script are executed on top of the running build container.
This is done so interactive web terminal have the same behavior as kubernetes, where even after the main script is done the user stays connected to the web terminal.
e as kubernetes
and shell
executor
When using docker in docker the --link
does not seem to work at all when we run docker exec
on the container. I have opened a question in https://forums.docker.com/t/cant-access-docker-socket-with-docker-exec/59190 but I might open an issue upstream for this. Even though I'm pretty sure it will not be supported since --link
is deprecated and docker in docker is being phased out.
For context please read the following issue
docker-ssh
shouldn't need any changes right?master
- branch was rebasedcloses #3605