-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
Nodejs inside docker image using dockerTools.buildImage cannot start in NixOS (but starts in Ubuntu) #170279
Comments
Googling leads to links that say that this is due to some ulimits problem. Not sure why nixos docker containers are having this problem. |
I've done some further testing. I've built the same image using the above expression. If I try to run it on NixOS docker, I get the above error. If I put it into an Ubuntu 22.04 LTS virtual machine I believe this is a NixOS problem. My docker configuration on NixOS is simple:
|
If anybody else wants to confirm, you can build the docker image from here: https://github.com/MatrixAI/TypeScript-Demo-Lib.
Note that the repo is a more sophisticated version of the above expression. I simplified the above expression to make the issue report easier. |
Look like this docker bug affects Ubuntu 22.04 too, see Tzahi12345/YoutubeDL-Material#610. However that could be a CI/CD option. |
It's possible that some default docker configuration has changed recently. |
Doesn't appear to happen anymore. |
Describe the bug
When using
dockerTools.buildImage
with justnodejs
as the only contents, it is not possible to run the/bin/node
inside the container in NixOS. But it does work in Ubuntu 22.04.Steps To Reproduce
Steps to reproduce the behavior:
Build that with
nix-build
ornix repl
, and then load it and run:Results in:
Expected behavior
It should just run the node repl.
Additional context
Add any other context about the problem here.
Metadata
I'm pinned on a5774e7 as the nixpkgs commit revision.
Running on NixOS
And my NixOS nixpkgs revision is d89f18a
The text was updated successfully, but these errors were encountered: