Scenario 2: DIND exploitation: Update deployment.yaml #177
Conversation
This file contains 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
The path to the Unix domain socket has been changed. Otherwise you don't get access to the host's container runtime environment. Important so that Scenario 2 (DIND) can be carried out. *Works for the Minikube
|
I understand the issue @kludee I think we somehow need to handle both cases of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Im using the Minikube. When i tried to access the host’s container runtime, with Containerd, ctr and docker i got an empty table or different errors which ended to be rabit holes.
The installed different Docker-Binaries to get an Workaround and saw that docker usese the Domain-Unix-Socket /run/docker.sock when starting dockerd.
So I changed the Unix-domain-socket in the deployment.yaml from /run/containerd/containerd.sock to /run/docker.sock and it worked. Otherwise i did not get access to the host's container runtime environment.
I suspect that Kubernetes is using the Unix-socket containerd.sock and this is causing problems. I'll investigate the behavior more closely as soon as I have more time.
Works for the Minikube
I am not aware of the impact it would have on other deployments.