-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
haskellPackages.stack doesn't properly have network access (when run inside Docker) #15168
Comments
This error happens when /etc/protocols doesn't exist. I've accidentally made Docker images without this file and had exactly the same problem with Haskell code. We need to add "iana_etc" to the Docker images. |
Hi @puffnfresh,
What else would I have to bind in the container? |
I just tried with adding |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
Sounds like this was solved by adding certs and |
Issue description
Context: we're trying out nix inside docker images, because in our environment it's easier to get access to machines with multi-user Docker installs than with multi-user nix setups.
The problem is with the "stack" executable. The observed behavior is that all stack commands fail, because when they try to reach for the network, they get an error. But other binaries that use networking work just fine. For example, I can execute
wget
commands within the container.I'm not yet sure if this is a problem with stack or a problem with the base images distributed on Docker hub by the user/org "nixos". I assume these are "official" based on the name?
Steps to reproduce
Put the following text in a Dockerfile, and run
docker build .
.The output will end with:
Technical details
The text was updated successfully, but these errors were encountered: