-
Notifications
You must be signed in to change notification settings - Fork 103
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
mirror d container - running from abnother container with mounted docker sock #2778
Comments
Hi, what mirrord version are you using? |
mirrord 3.117.0 same as agent |
This looks like an issue we fixed with mirrord 3.118.0 can you try it please ? |
still same on version mirrord 3.118.0 |
Oh I've just noticed you have a custom repo for mirrord-agent the issue might be pulling sidecar image that we spawn for container feature, could you try and add this to your config with the updated registry? "container": {
"cli_image": "***our mirror***/metalbear-co/mirrord-cli:3.118.0"
} |
Error still persisit: as error is
i would say container was living for some time... (image was pulled) - but just my quess con figuration now looks like:
|
Hi I may have missed this but just to clarify the image of the cli is a bit different from the agent image ghcr.io/metalbear-co/mirrord-cli - cli-image Can you double check because I see that the provided config does have the same image in both config values |
Woow, thanks i totally missed fact of two different images. Let me add it to my corporate mirror and try it. |
Still persist: command:
mirror_dee_tmp_conf.json :
error: ! mirrord container is currently an unstable feature |
Ah that's a bummer, there is this one fix that we just released with version Could you try and update to latest version? this might shed more light on what is the problem |
Bug Description
First let me expalin my settings:
i have everything installed in container, kubectl, google cloud sdk in order to work with our infrastructure running in GKE, docker sock is mounted from host.
i have also installed mirrorD in container although kubectl, docker is working i get errors when trying to use
mirrod container
i know, bit weird setup, i love it see working. in same setup i can use
mirrord exec
without issues.mirrord command:
mirrord container -f mirror_dee_tmp_conf.json -- docker run -p 8383:8080 mendhak/http-https-echo
content of mirror_dee_tmp_conf.json :
error i got:
logs from docker deamon running in debug mode:
Steps to Reproduce
mirror d instalation in container
kubectl installation in container
docker sock mounted from host
running
mirrord exec...
Backtrace
No response
Relevant Logs
No response
Your operating system and version
container os: Linux 67bb1e5e3dc1 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 aarch64 GNU/Linux computer os: Darwin Michals-MacBook-Pro.local 22.6.0 Darwin Kernel Version 22.6.0: Mon Jun 24 01:22:14 PDT 2024; root:xnu-8796.141.3.706.2~1/RELEASE_ARM64_T6000 arm64
Local process
running mirrord container
Local process version
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: