-
Notifications
You must be signed in to change notification settings - Fork 184
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
Unable to activate a shell because of a network error. I am unable to work. #1977
Comments
I tried removing the
Hope this helps |
Hey @carlotm, you're right that we shouldn't be preventing a shell if packages are already downloaded. I think there are two things I'll look into here:
For the second one, are you connected to a VPN? Do you know how you have DNS configured? It looks like Go is trying port 53 on localhost, which doesn't have anything listening. I think Go now defaults to not using glibc for lookups, which could explain why curl works but Devbox doesn't. |
Thank you, I double checked and indeed my dns wasn't resolving correctly, ( I am still not sure why devbox needs to fetch anything remotely if I have the packages already installed, Cheers! |
@carlotm the issue is my original fix in #1657 was just a hack. unfortunately my follow up fix is a hack as well (check description for a bit of what is going on). Theses fixes are mostly bandaids that catch some network failures, but not all. In terms of why it works this way, the (kinda) short answer is:
We don't need to actually check the remote cache because the lockfile has enough information to check the local cache on your machine. But doing this is a much bigger change that would require some rearchitecting. In the meantime, #1985 is an easy solution that would allow you to continue working in offline mode if DNS resolution fails. |
## Summary Fixes #1977 (with another hack). Unfortunately the way we structure our flake makes it really difficult to remove our network requests (when state is stale). Ideally, the flake can be built off of local only nix store references, but that's a much bigger project. In the meantime, this is a quick hack that fixes issue above. ## How was it tested? Added synthetic error that returns `connection refused` in the message. Ensures I was still able to run/shell with a stale state.
What happened?
This morning I tried to activate a shell (
devbox shell
), the same shell I activate every day at work.I got this error:
I have to mention I can wget that url correctly.
I believe one should be able to use devbox offline without issues if packages are already downloaded.
I opened an issue some time ago, which was promptly resolved (#1657)
I don't know if this is the same issue, but it's preventing me from being able to work, which is quite annoying, honestly.
Cheers!
Carlo
Command
shell
devbox.json
Devbox version
0.10.4
Nix version
nix (Nix) 2.17.1
What system does this bug occur on?
Linux (x86-64)
Debug logs
The text was updated successfully, but these errors were encountered: