Docker-in-docker: Updates docker-init with "pkill" #711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes : devcontainers/images#729
When the universal image is built with latest
docker-in-docker
Feature, it fails to start docker daemon ascontainerd
does not start (Reported in #671 (comment)) .The image is trying to retry the docker daemon startup, but ascontainerd
(or/anddockerd)
is not in a good state before, it fails to restart causingdocker ps
to fail.We do have these commands ^ but it simply removes the PID files, does not stop/clean the dockerd and containerd daemons
🧪 Tested these PR changes with
universal:dev@sha256:b7a147f15c61f02b8220d1719431f205f65e48267ffed93e0b9c642c14cf956a
image,docker ps
is successful.