Open acaloiaro opened 4 months ago
This may be related to some instances of #700
Having the exact same issue with node provider. The node_modules folder must be removed in order to nixpacks build
to succeed. sudo nixpacks
works, but I don’t feel comfortable doing that. Even when the build is running as root, the absolute slowness when trying to copy the entire modules directory to the build context almost halts the entire process. Any way we can ignore files like honouring the .gitignore
or even a .nixpacksignore
?
I should add if you're having this permission problem and you're okay with setting all permissions within a particular directory to read/write, the following will fix permissions, e.g. ./node_modules
: find ./node_modules -perm 444 -exec chmod 0600 {} \
@acaloiaro is there a way for this directory to not be copied at all?
Is there an existing issue for this?
Describe the bug
When projects being built by
nixpacks
contain read-only files,nipacks build ...
results in a permission error due to Rust's fs::copy retaining file permissions, and nixpacks rewriting all CRLF line endings with LF: https://github.com/railwayapp/nixpacks/blob/2ec70b75709af40db28762a77a3c98aaaebb09ad/src/nixpacks/files.rs#L35To reproduce
In any project to be built by nixpacks, on a Linux system
Here from the
strace
output, we can see that the permission error occurs openingtest
as writableAnd
stat
shows us that that file retained its original read-only permissions, preventing the writable file handleExpected behavior
Environment
OS: NixOS Unstable Kernel: Linux version 6.6.17 (nixbld@localhost) (gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.40) #1-NixOS SMP PREEMPT_DYNAMIC Fri Feb 16 18:10:57 UTC 2024 Nixpacks version: 1.20.0 / any