Nix Packs not building becasue of rate limits
story-boards-ai
PROOP

10 months ago

error:
[stage-0 4/12] RUN nix-env -if .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix && nix-collect-garbage -d
"nix-env -if .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix && nix-collect-garbage -d" did not complete successfully: exit code: 1

View in context

unpacking 'https://github.com/NixOS/nixpkgs/archive/ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.tar.gz' into the Git cache…

error:
… while calling the 'import' builtin
at /app/.nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix:3:12:
2|
3| let pkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.tar.gz") { overlays = [ (import (builtins.fetchTarball "https://github.com/railwayapp/nix-npm-overlay/archive/main.tar.gz")) ]; };
| ^
4| in with pkgs;
… while realising the context of a path
… while calling the 'fetchTarball' builtin
at /app/.nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix:3:20:
2|
3| let pkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.tar.gz") { overlays = [ (import (builtins.fetchTarball "https://github.com/railwayapp/nix-npm-overlay/archive/main.tar.gz")) ]; };
| ^
4| in with pkgs;
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: Failed to open archive (Source threw exception: error: unable to download 'https://github.com/NixOS/nixpkgs/archive/ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.tar.gz': HTTP error 404
response body:
404: Not Found)

happens in all my deployments

Solved

5 Replies

story-boards-ai
PROOP

10 months ago

272cc306-832f-42e6-a34c-9e564719a95d


story-boards-ai
PROOP

10 months ago

Did you just update the nixpacks versions? Becasue the default ones error out


story-boards-ai
PROOP

10 months ago

Just added these envs:
NIXPACKS_NIXPKGS = nixos-23.11

this seems to work


10 months ago

Hello,

This was caused by a transient upstream issue, something completely out of our control unfortunately.

The variable you set did not actually resolve anything, what resolved the issue was the redeploy caused by setting a variable.

Best,
Brody


10 months ago

!s


Status changed to Solved brody 11 months ago


Loading...