Open
Conversation
maxknee
force-pushed
the
mk/update-docker
branch
from
fda500f to
427c9fc
Compare
Signed-off-by: Max Knee <max.knee@nytimes.com>
maxknee
force-pushed
the
mk/update-docker
branch
from
427c9fc to
19d0d55
Compare
Member
|
@maxknee Could you please share more details about the issue you encountered? Does upgrading the Docker dind image to this exact version |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updating latest docker in docker.
We are seeing an issue with the latest 6.18 linux kernel:
latest: Pulling from plugins/gcr Digest: sha256:6d47e0f5c7f3e23018d9d9235129ed2df47f7ab67a2fa566aba33176fe52dd56 Status: Downloaded newer image for plugins/gcr:latest + /usr/local/bin/dockerd --data-root /var/lib/docker --host=unix:///var/run/docker.sock --dns 10.248.2.2 Unable to reach Docker Daemon after 15 attempts.