Loading...

nix error on deploy

k1ng0hatTRIAL

a year ago

#8 8.217

Jun 05 16:10:29

#8 8.217 … while calling the 'fetchTarball' builtin

Jun 05 16:10:29

#8 8.217 at /app/.nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix:3:20:

Jun 05 16:10:29

#8 8.217 2|

Jun 05 16:10:29

#8 8.217 3| let pkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.tar.gz ";) { overlays = [ (import (builtins.fetchTarball "https://github.com/railwayapp/nix-npm-overlay/archive/main.tar.gz ";)) ]; };

Jun 05 16:10:29

#8 8.217 | ^

Jun 05 16:10:29

#8 8.217 4| in with pkgs;

Jun 05 16:10:29

#8 8.217

Jun 05 16:10:29

#8 8.217 error: cannot read file 'nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db/pkgs/development/haskell-modules/hackage-packages.nix' from tarball

Jun 05 16:10:29

#8 ERROR: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d" did not complete successfully: exit code: 1

Jun 05 16:10:29

-----

Jun 05 16:10:29

> [ 4/12] RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d:

Jun 05 16:10:29

8.217 … while realising the context of a path

Jun 05 16:10:29

8.217

Jun 05 16:10:29

8.217 … while calling the 'fetchTarball' builtin

Jun 05 16:10:29

8.217 at /app/.nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix:3:20:

Jun 05 16:10:29

8.217 2|

Jun 05 16:10:29

8.217 3| let pkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.tar.gz ";) { overlays = [ (import (builtins.fetchTarball "https://github.com/railwayapp/nix-npm-overlay/archive/main.tar.gz ";)) ]; };

Jun 05 16:10:29

8.217 | ^

Jun 05 16:10:29

8.217 4| in with pkgs;

Jun 05 16:10:29

8.217

Jun 05 16:10:29

8.217 error: cannot read file 'nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db/pkgs/development/haskell-modules/hackage-packages.nix' from tarball

Jun 05 16:10:29

-----

Jun 05 16:10:29

Dockerfile:8

Jun 05 16:10:29

-------------------

Jun 05 16:10:29

6 |

Jun 05 16:10:29

7 | COPY .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix

Jun 05 16:10:29

8 | >>> RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d

Jun 05 16:10:29

9 |

Jun 05 16:10:29

10 | COPY .nixpacks/assets /assets/

Jun 05 16:10:29

-------------------

Jun 05 16:10:29

ERROR: failed to solve: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d" did not complete successfully: exit code: 1

Jun 05 16:10:29

Error: Docker build failed

14 Replies

zuchkaPRO

a year ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

k1ng0hatTRIAL

a year ago

help pls

brodyEMPLOYEE

a year ago

full build logs please -

https://bookmarklets.up.railway.app/log-downloader/

k1ng0hatTRIAL

a year ago

this is my full log

Attachments

logs.txt

brodyEMPLOYEE

a year ago

That would not be your full build logs, please use the bookmarklet.

ss-witBIZCLASS

a year ago

Experiencing the same issue, but my error line is for a different package. Seems like something flaky with nixpacks? This is before it gets to steps to build/run any of my code, iiuc.

error: cannot read file 'nixpkgs-bf446f08bff6814b569265bef8374cfdd3d8f0e0/pkgs/by-name/uv/uv/Cargo.lock' from tarball

Full build logs attached

Attachments

build_logs_...

jrEMPLOYEE

a year ago

Can you please share more about services/builds. Which service is experiencing these failures? Does it continue to happen on a redeploy?

ss-witBIZCLASS

a year ago

The service/builds are happening for various apps, mostly typescript/node/next from a monorepo as you can see in the build logs.Redeploys seem to work fine typically, but obviously unideal to have the builds fail and have to investigate so frequently (happens ~daily for us)