linear[bot]
commented
2 months ago Open miob-miob opened 2 months ago
linear[bot]
commented
2 months ago 
aviramha
commented
2 months ago Hi, what mirrord version are you using?
miob-miob
commented
2 months ago mirrord 3.117.0
same as agent
aviramha
commented
2 months ago This looks like an issue we fixed with mirrord 3.118.0 can you try it please ?
miob-miob
commented
2 months ago mirrord container -f mirror_dee_tmp_conf.json -- docker run -p 8383:3333 mendhak/http-https-echo
! mirrord container is currently an unstable feature
x ! mirrord container is currently an unstable feature
✓ preparing to launch process
✓ operator not found
✓ container created
✓ container is ready Error: × Command failed to execute command [docker logs f28c1b6b0de277f79feb429dd29804baf8400d76ee87091f913766783950fc86]: Error: No such container:
│ f28c1b6b0de277f79feb429dd29804baf8400d76ee87091f913766783950fc86
│
help: This is a bug. Please report it in our Discord or GitHub repository.
still same on version mirrord 3.118.0
DmitryDodzin
commented
2 months ago 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
docker logs a12cf054f069f17cd830eb0be27ead026167ae1a311954a1aa0baf5cbf368818]: Error: No such container: a12cf054f069f17cd830eb0be27ead026167ae1a311954a1aa0baf5cbf368818
i would say container was living for some time... (image was pulled) - but just my quess
con figuration now looks like:
"target": {
"pod": "cocoaas-backoffice-ccdb58b7f-kvwvh",
"container": "cocoaas-backoffice"
},
"container": {
"cli_image": "*******/mirror-eu/ghcr.io/metalbear-co/mirrord:3.118.0"
},
"agent": {
"labels": {
"app": "mirrord",
"team": "mirrord"
},
"ephemeral": true,
"image": "*****mirror-eu/ghcr.io/metalbear-co/mirrord:3.118.0",
"annotations": {
"cluster-autoscaler.kubernetes.io/safe-to-evict": "true"
},
"privileged": false
},
"feature": {
"hostname": true,
"network": {
"incoming": {
"mode": "steal",
"ignore_localhost": false
}
}
}
}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 ghcr.io/metalbear-co/mirrord - agent-image
Can you double check because I see that the provided config does have the same image in both config values
miob-miob
commented
1 month ago Woow, thanks i totally missed fact of two different images. Let me add it to my corporate mirror and try it.
miob-miob
commented
1 month ago Still persist:
command:
mirrord container -f mirror_dee_tmp_conf.json -- docker run -p 8383:8080 mendhak/http-https-echo
mirror_dee_tmp_conf.json :
{
"target": {
"pod": "cocoaas-backoffice-64f4bcd458-v9575",
"container": "cocoaas-backoffice"
},
"container": {
"cli_image": "INTERNAL-MIRROR/ghcr.io/metalbear-co/mirrord-cli:3.118.0"
},
"agent": {
"labels": {
"app": "mirrord",
"team": "mirrord"
},
"ephemeral": true,
"image": "INTERNAL-MIRROR/ghcr.io/metalbear-co/mirrord:3.118.0",
"annotations": {
"cluster-autoscaler.kubernetes.io/safe-to-evict": "true"
},
"privileged": false
},
"feature": {
"hostname": true,
"network": {
"incoming": {
"mode": "steal",
"ignore_localhost": false
}
}
}
}error:
! mirrord container is currently an unstable feature x ! mirrord container is currently an unstable feature ✓ preparing to launch process ✓ operator not found ✓ container created ✓ container is ready Error: × Command failed to execute command [docker logs │ 486768d9040d698a3544344b740f56690f1a1e64bd80564ae9676f940ffe45f2]: Error: No such container: │ 486768d9040d698a3544344b740f56690f1a1e64bd80564ae9676f940ffe45f2 │
DmitryDodzin
commented
1 month ago Ah that's a bummer, there is this one fix that we just released with version 3.121.1 that should update the error to a more correct error message, like I'm afraid the docker logs <id> error is just because the sidecar is deleted before the cli managed to get the error logs (the latest release should fix it)
Could you try and update to latest version? this might shed more light on what is the problem
aviramha
commented
3 weeks ago @miob-miob did you have time to try out @DmitryDodzin suggestion?
miob-miob
commented
3 weeks ago Let me try it tomorrow.
miob-miob
commented
3 weeks ago Hi Guys output is different, seems empty :(
aviramha
commented
1 day ago Can you try 3.125.2 please?
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 containeri know, bit weird setup, i love it see working. in same setup i can use
mirrord execwithout issues.mirrord command:
mirrord container -f mirror_dee_tmp_conf.json -- docker run -p 8383:8080 mendhak/http-https-echocontent 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