Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DIND (docker-in-docker) scenario missing tar binary, unable to complete scenario #80

Closed
mrintern opened this issue Oct 4, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@mrintern
Copy link

mrintern commented Oct 4, 2022

@madhuakula
In scenario 2, DIND, tar is required to unzip the docker binary we download from the internet using wget. /usr/bin/tar is missing, preventing one from completing the scenario.

I actually tried grabbing tar from my local machine using wget to complete the scenario but I wasn't able to get it to work, and it's difficult to understand whats wrong without a shell (all i see from the ping service is exit codes)

Am I missing something? Seems to me like the scenario is broken. I ran through the first scenario without issues.

My setup:

  • windows subsystem for linux 2 (WSL2) (ubuntu app)
  • Windows 11 underneath that
  • deployed K8S goat using KinD
@madhuakula madhuakula self-assigned this Oct 6, 2022
@madhuakula
Copy link
Owner

Hi @mrintern

Thanks for reporting this. Unfortunately I don't have the WSL setup to test. But looking at its mostly issue with the binaries and the environment you are running, let me revamp the scenario execution environment to work seamlessly for everyone regardless of environment.

Hopefully I will try to make a fix by this weekend.

@madhuakula madhuakula added the enhancement New feature or request label Mar 8, 2023
@madhuakula madhuakula moved this to 🌳 Backlog in Kubernetes Goat Mar 8, 2023
@madhuakula madhuakula moved this from 🌳 Backlog to 👉 To do in Kubernetes Goat Mar 8, 2023
@madhuakula
Copy link
Owner

I think you can leverage the static binaries in the pod https://download.docker.com/linux/static/stable/. Not sure if this helps in the WSL setup, I would also recommend checking two things

  1. Container runtime
  2. Support the downloaded container binary (docker, ctr, etc.) so you can interact with the respective socket.

@madhuakula madhuakula moved this from 👉 To do to 🧐 Review in Kubernetes Goat Apr 2, 2023
@madhuakula
Copy link
Owner

It should be fixed with the recent fix from #150

@madhuakula madhuakula moved this from 🧐 Review to ✅ Done in Kubernetes Goat Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants