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
problem building a nixpack under gitpod #82
Comments
Do you have a lockfile? If not, please generate one with |
doesn't the example node project already have a lockfile. also, this command worked when run on my Mac. |
this is what the example project has
|
Looks like there was trouble starting a thread in V8. I don't know why that would be, though, unless Gitpod has a limit on running threads (?), which I can't find mention of in their pricing. |
Building the generated Generated Dockerfile for node-main-file example
ulimit logs for Container(Layer 13)
ulimit logs for Gitpod
|
Related NixOS/nixpkgs#170279 |
I think @wyzlle is on the right track. If I have a standard Dockerfile, I can build the image in gitpod. But the one that nixpacks generates using nix for packaging fails. Also, I tried the go and python examples and they also fail under gitpod. |
Anyone had a chance to look at this? I have worked with gitpod and they believe it has to do with the way that nix is installed. One thing I noticed is that nix is installed as root. The docs recommend not to do this. |
If you can reproduce that using nix via root causes this, and using it via not root fixes it, we'd be happy to fix that Beyond that, we're a bit limited on bandwidth ATM but you're welcome to take a crack at it yourself, or have one of the Gitpod people do jump into it |
Closing for inactivity. We do also have a devcontainer setup in the Nixpacks repo that a few users use https://github.com/railwayapp/nixpacks/tree/main/.devcontainer |
I am using gitpod as my dev environment as I learn about nixpacks. I can build the binary without any problem but I can't build a nitpack for the example node project. I'm not very familiar with rust so not really clear what the error message is indicating.
Note, I am able to build locally on my Mac so its something to do with the gitpod environment. It looks like it fails doing a
npm ci
at the end of the docker build. My Mac has node 17 while gitpod is 16. Not sure if that's important.To reproduce the issue, create a gitpod workspace using
https://gitpod.io/#
+ the GitHub repo URL. Then from the terminal runcargo run -- build examples/node --name node
Here is the output.
The text was updated successfully, but these errors were encountered: