-
Notifications
You must be signed in to change notification settings - Fork 56
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
Random "Is the docker daemon running?" with Docker-in-Docker Feature #192
Comments
@Chuxel Any thoughts on this? |
Hmmm. If you add Adding a sleep statement in the exec might also verify whether this is a race condition. |
Seems Docker does not start at all. Also, when this happens there is no amount of waiting I can do in the devcontainer. Docker will just not work. I tried waiting for several minutes.
|
Looking at https://github.com/customink/dnd-demo/actions/runs/3990966349/jobs/6845376920#step:3:689, this issue sounds quite similar to devcontainers/features#372 Looks like this issue mostly occurs in Action runners & not in a Codespace. |
@metaskills Even the other issue I pointed at, uses the |
Sure. I'll change it to a few other things and even see if the version of the CI helps. Will report back shortly. |
So I tested |
Very strange. I'd also be curious if running the |
Do you mean in my |
We've had internal reports of this as well with Debian 11. |
Yes, sorry. (Under the hood its |
Created actions/runner-images#6980 |
@Chuxel Tried that... did not help. The message is still the same when I do this.
|
Originally posted by @Alexey-Ayupov in actions/runner-images#6980 (comment) @metaskills Would you be interested to test this hypothesis? Thanks! |
Thanks, I'm subscribed to that issue too so I replied there. |
When using the docker in docker feature it has a 20% chance to fail. I created a demo repo to show case this. It uses concurrent jobs to highlight the issue well but is not limited to this workflow style. I am seeing this random failure behavior all over certain project. HELP PLEASE!
If this issue is within the CLI, then I have created an issue there in that project to track it as well:
The text was updated successfully, but these errors were encountered: