a year ago
My application builds stopped working, I already tried to re-deploy a version that was in production and it also failed
Erros:
```
[stage-0 4/8] RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d:
24.09
24.09 (stack trace truncated; use '--show-trace' to show the full, detailed trace)
24.09
24.09 error: attribute 'dev' missing
24.09 at /app/.nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix:19:13:
24.09 18| '')
24.09 19| gcc postgresql.dev python38
24.09 | ^
24.09 20| ];
24.09 Did you mean doc?
Dockerfile:8
6 |
7 | COPY .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix
8 | >>> RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d
9 |
10 |
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
Error: Docker build failed```
36 Replies
a year ago
I also have this error, I thought it was the only one
I'm also trying to rebuild old working versions and they don't work either.
a year ago
please send your entire build logs + any manual configuration files you have (eg. nixpacks.toml)
Procfile:
web: python manage.py migrate && python manage.py collectstatic --noinput & pip install -r requirements.txt & gunicorn core.wsgi
FWIW I'm getting sudden build failures without any changes in configuration, went from healthy to failing with just the redeploy option
It looks like my NodeJS version was switched from 22 to 23 without any config changes, wondering if that's related. Maybe check previous success and error logs and see if library versions have changed.
Here, in some attempts, it also appears that an environment variable domain does not exist, even though it has been configured
a year ago
!team
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response adam • about 1 year ago
a year ago
Raised this to the team, this seems like a platform issue.
Changing the NodeJS version via an environment variable for the Nixpacks Node version fixed the build for me
a year ago
@Medikornov @Caio sampaio can you try the above and lmk if it works?
a year ago
ah, my mistake. The issues may be unrelated then, i’ll dig into your config some more
I don't know if it applies to Docker, but check that the same versions of Python and Django are still being used in the failing builds
a year ago
Since a dockerfile was used, the versions should be locked
a year ago
@Caio sampaio mind sending your requirements.txt?
amqp==5.1.1
asgiref==3.6.0
async-timeout==4.0.2
Babel==2.12.1
backports.zoneinfo==0.2.1
billiard==3.6.4.0
black==22.1.0
blue==0.9.1
cachetools==5.3.0
celery==5.2.7
certifi==2022.12.7
charset-normalizer==3.0.1
click==8.1.3
click-didyoumean==0.3.0
click-plugins==1.1.1
click-repl==0.2.0
coverage==7.2.2
Deprecated==1.2.13
Django==4.1.5
django-celery-beat==2.4.0
django-celery-results==2.4.0
django-debug-toolbar==4.0.0
django-js-asset==2.0.0
django-mathfilters==1.0.0
django-model-utils==4.3.1
django-notifications-hq==1.7.0
django-object-actions==4.2.0
django-pwa==1.1.0
django-storages==1.13.2
django-timezone-field==5.0
django-tinymce==3.6.1
docker-py==1.10.6
docker-pycreds==0.4.0
docutils==0.19
flake8==4.0.1
freetype-py==2.3.0
google-api-core==2.11.0
google-auth==2.16.0
google-cloud-core==2.3.2
google-cloud-storage==2.7.0
google-crc32c==1.5.0
google-resumable-media==2.4.1
googleapis-common-protos==1.58.0
gunicorn==20.1.0
idna==3.4
imagesize==1.4.1
importlib-metadata==6.5.1
Jinja2==3.1.2
jsonfield==3.1.0
kombu==5.2.4
MarkupSafe==2.1.2
mccabe==0.6.1
mypy-extensions==1.0.0
packaging==23.1
pathspec==0.11.1
Pillow==9.4.0
platformdirs==3.1.1
prompt-toolkit==3.0.36
protobuf==4.21.12
psycopg2-binary==2.9.5
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycodestyle==2.8.0
pyflakes==2.4.0
PyJWT==2.8.0
pysendpulse==0.1.4
python-crontab==2.7.1
python-dateutil==2.8.2
python-decouple==3.7
python3-memcached==1.51
pytz==2022.7.1
redis==4.4.2
requests==2.28.2
rsa==4.9
six==1.16.0
snowballstemmer==2.2.0
sphinx==6.1.3
sphinxcontrib-applehelp==1.0.4
sphinxcontrib-devhelp==1.0.2
sphinxcontrib-htmlhelp==2.0.1
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.3
sphinxcontrib-serializinghtml==1.1.5
sqlparse==0.4.3
stripe==5.2.0
swapper==1.3.0
tomli==2.0.1
typing-extensions==4.5.0
tzdata==2022.7
urllib3==1.26.14
vine==5.0.0
wcwidth==0.2.6
websocket-client==1.6.1
whitenoise==6.3.0
wrapt==1.14.1
zipp==3.15.0I'm using Python with fast api
this is the error i'm getting:ERROR: failed to solve: process "/bin/bash -ol pipefail -c python -m venv --copies /opt/venv && . /opt/venv/bin/activate && pip install poetry==$NIXPACKS_POETRY_VERSION && poetry install --no-dev --no-interaction --no-ansi" did not complete successfully: exit code: 1
a year ago
I'm leaning towards this being a nixpacks issue, the build isn't getting through the initial setup
a year ago
Please open a new thread, your issue is likely different than this
specifying nixpacks version to 1.29.1 fixed the issue for me. Should the 1.30 version break things like that?
a year ago
No, it should not. Noting that for the team
a year ago
Breaking things was definitely not intended. We've reverted to 1.29.1 on Railway for now
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Those with failed builds, can you please link to the deployments so we can look into what broke.
a year ago
After reverting it is working here.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
!s
Status changed to Solved adam • about 1 year ago
jr
Those with failed builds, can you please link to the deployments so we can look into what broke.
10 months ago
Hi,
Was this is resolved.? Am experiencing the same . How do I go about it?
1af56524-778f-4958-a325-3482bc58d12a
Status changed to Open Railway • 11 months ago
lbwaks
Hi,Was this is resolved.? Am experiencing the same . How do I go about it? 1af56524-778f-4958-a325-3482bc58d12a
10 months ago
Please open your own thread.
Status changed to Closed brody • 11 months ago