-
Notifications
You must be signed in to change notification settings - Fork 295
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
[Container] Fail to build a devcontainer: ERROR: failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF #7958
Comments
Same here. |
It seems to be the docker upgrade, see #7955 |
Same here, glad I'm not alone, it was driving me crazy. I succeed to make it works by disabling all Dev Container Features in my |
I've tried to deactivate almost everything, but in my case the error still occurs. |
Same here, the issue comes from the upgrade of Docker, thanks @pglira to point me out the closed issue. Maybe the issue comes from the new default builder, I don't know: As for now, I'll leave this issue opened, just to continue to investigate. |
I found maybe a possible relating problem while digging into buildx issues: docker/buildx#1325. |
I downgraded docker to 20.10.23 and now it works again. For this I followed the instructions here: https://docs.docker.com/engine/install/ubuntu/ (I'm on Ubuntu 22.04) (However, it did not work immediately. For some reason I needed to reinstall also docker-desktop and to restart my pc twice but this might not be necessary in other cases.) |
Tracking devcontainers/cli#398. |
Same here 🥲 |
same :( |
same here (on my open source project: https://github.com/antonioconselheiro/bater-ponto) |
Had the same problem, docker-compose build worked but vscode devcontainers builds are failing with the same issue. Downgrading to 20.10.23 fixed the problem |
Workaround without changing docker version, if using linux is to add Restart vscode and I was able to build the container again. |
Plopping in a snippet of the error for search engines in case other people run into this:
I hope there is a fix soon! |
We got an answer in docker buildx project, a fix is in the pipe: docker/buildx#1325 (comment) |
Easy workaround until the fix is live is to disable inline cache in devcontainer.json :
|
@elcojacobs 's workaround worked for me |
I also found out that the slowest part of a container rebuild here was pushing it to the inline cache, which somehow took 10 minutes. Just rebuilding from the registry cache finishes in 10 seconds, so I might leave the inline cache disabled. Not sure what the benefit would be if we keep a registry container up-to-date. |
Doing the community a service. Thank you! |
Same error here. After three hours of frustration I finally found this issue. I'm gonna downgrade Docker now to see if I'm lucky |
Same error, downgraded to v20 and it fixed it. |
Same problem on Ubuntu with Docker v23 today. Downgrade to v20 resolved the problem. |
this one works perfectly fine as tmp. solution. Thanks @elcojacobs ! |
I faced the same problem and resolved by executing command
Docker v23 uses BuildKit to build container images as default, and uses docker-own fallback instanse if no buildkit instance created. I think the fallbak instance has some problems... |
The downgrade worked on fedora too.
replace the first package on both lines with the current docker version |
It's work! Thanks a lot! |
For a remote machine with multiple users, doing the following two fixed it for now:
# add the following line in /etc/bash.bashrc
export DOCKER_BUILDKIT=0
"args": {
"BUILDKIT_INLINE_CACHE": "0"
} I didn't remove docker-buildx-plugin or downgrade Docker. Just restarted vscode after settings the two. |
Spent a day with the same problem. My devcontainer builds a The solution for me was to do both actions mentioned by @Uguudei (just 1 was not enough). For reference if you're using |
Omg! I was trying to debug this issue by manually running the |
I used docker-compose for devcontainer so build args option in |
@akhildevelops Yes same here, adding "BUILDKIT_INLINE_CACHE": "0" to args in the devcontainer.json solved the problem for me to this is the only error that I found printed in journalctl after starting the devcontainer |
@Oblynx Where exactly in your services:
app:
build:
context: .
dockerfile: Dockerfile
args:
BUILDKIT_INLINE_CACHE: 0 |
@algodave For me it worked adding
Also, remove previous containers with |
It is fixed in Docker v23.0.1. Just update docker and it works fine. |
Ref: #7958 (comment) Thanks upgrading to |
Seems that we could close this bug now? |
I guess we can, since the new version of Docker 23.0.1 has been released. |
@algodave I think you're missing quotes, YAML might be messing up the parameter type otherwise. Try with |
VSCode Version: 1.75
Local OS Version: Fedora 37
Remote OS Version: Fedora 37
Remote Extension/Connection Type: Containers
Logs:
Steps to Reproduce:
I don't know what is causing this issue, this morning I upgraded at the same time, VSCode to 1.75 and Docker to 23.0.0. I think one of them seems to have triggered this issue I didn't have yesterday.
The text was updated successfully, but these errors were encountered: