a year ago
Previously, by support, I specified a specific version of Nixpacks, and that allowed it to build, but I believe that version 14 is definitely out of spec now.
My code is in a github repository, so it's available to view, and no significant differences have happened in quite a long time.
The project is actively being used (registration for a Friday morning children's group), so I'd prefer not to take down the current instance.
I hope that something obvious can be seen.
Jon
--
10 32.11 error: Unable to build profile. There is a conflict for the following files:
10 32.11
10 32.11 /nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/include/node/node_buffer.h
10 32.11 /nix/store/3ivm2pca8l4f3svwwpmxqjncj5a1h237-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env/include/node/node_buffer.h
10 32.15 error: builder for '/nix/store/9qhyaj53164ghxb4qw7mkcq3lvx49gbr-user-environment.drv' failed with exit code 1
10 ERROR: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d" did not complete successfully: exit code: 100
[stage-0 6/21] RUN nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d:
32.02 sourcing setup hook '/nix/store/xyff06pkhki3qy1ls77w10s0v79c9il0-reproducible-builds.sh'
32.02 sourcing setup hook '/nix/store/ngg1cv31c8c7bcm2n8ww4g06nq7s4zhm-set-source-date-epoch-to-latest.sh'
32.02 sourcing setup hook '/nix/store/gps9qrh99j7g02840wv5x78ykmz30byp-strip.sh'
32.07 created 19 symlinks in user environment
32.10 building '/nix/store/9qhyaj53164ghxb4qw7mkcq3lvx49gbr-user-environment.drv'…
32.11 error: Unable to build profile. There is a conflict for the following files:
32.11
32.11 /nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/include/node/node_buffer.h
32.11 /nix/store/3ivm2pca8l4f3svwwpmxqjncj5a1h237-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env/include/node/node_buffer.h
32.15 error: builder for '/nix/store/9qhyaj53164ghxb4qw7mkcq3lvx49gbr-user-environment.drv' failed with exit code 1
Dockerfile:10
8 | RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d
9 | COPY .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix
10 | >>> RUN nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d
11 | RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends procps libpq-dev git curl autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm6 libgdbm-dev libdb-dev
12 |
ERROR: failed to solve: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d" did not complete successfully: exit code: 100
Error: Docker build failed
ⓘ Deployment information is only viewable by project members and Railway employees.
7 Replies
a year ago
Hello,
First off, you would definitely want to revert this commit -
https://github.com/t12nslookup/toddletime/commit/010f6d5a909b4b2981f86f695eb634deeab1b78d
You would need to have nixpacks fixed to a specific version for an older codebase like this.
a year ago
It's been failing with that version for the last 6 months. it's not working with nixpacks 14 any more, and as can be seen; that commit was today, just to see if the latest version made it work ...
Tbh, I'm happy with rebasing to a newer ruby/rails, if that's a permanent fix, but it's not without effort, and JavaScript libraries have moved on.
I can revert the nixpacks change but it will not fix the issue with the image generation.
a year ago
I don't run it as a docker image, but I run it in both WSL and Ubuntu environments, and it's really not a clever application.
Jon
a year ago
Then I think it would be best for you to write a Dockerfile that mimics your local environment as closely as possible, the Nixpacks environment is a bit of a black box if I'm being honest.
a year ago
I don't have a docker environment, at present, apart from railway. I'll go down that route, but also think again about migrating to a vanilla rails 8 environment and seeing how bad that change really is ... It's only a basic form setup with bootstrap, a couple of monkey wrenched time/date combo boxes and a devise authentication mechanism ... Really nothing too complicated ...
It was all running fine on heroku, until they got greedy with "hobby" systems, at which point I migrated to railway ... It's still running on here, but I can't build it with any "bundle update" for security, as it's not rebuilding.
I'll give the docker a read over, and see if I can get that working
Jon
a year ago
Don't worry about not having a local Docker environment. After all, I work for Railway, and I don't have Docker installed on any of my computers.
But I wish you the best of luck in writing a Dockerfile!