-
Notifications
You must be signed in to change notification settings - Fork 379
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
Fix in docker_inspect_self_mountinfo() fo Gitlab runner #1569
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
We further investigated the error which led us to our custom data-root setting in /etc/docker/daemon.json: The fallback implemented due to #1321 misses the container id because of our changed data-root to "docker-data" instead of default "docker". The real issue here is, that docker_inspect_self_mountinfo() wont work, if data-root setting contains no "/docker/". The current PR bears no value for other users now. Pseudocode:
|
This is currently blocking me and I have no authority over our agents. Is there something I can do as a workaround? |
if you add I think I have a workaround, I'll create a new PR and then you and @zweikaesehoch could maybe try it |
I have also run into this issue attempting to run cross on GitHub Codespaces. It seems local devcontainers use .filter(|s| s.contains("/docker/") || s.contains("/containers/"))``` although there may be a better way. |
Please give #1588 a try 👍🏼 |
Crossbuilding in our buildimage on a Gitlab runner failed:
Container ID could not be resolved from /proc/self/mountinfo, because "/docker/" string was expected, but "/docker-data/" provided:
I extended string matching with "/docker-data/" and our pipeline is working again.