apt-get update failing due to a missing GLIBC_2.36 version
Tried to find a resolution to this myself but I've ran out of options that I'm aware of for manipulating the underlying operating system.
Service I.D: e7c663db-2958-40f5-8413-0118a353df39
The only adjust was .env variables. The last build was successful.
Logs:
#9 [stage-0 5/14] RUN apt-get update && apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1 #9 1.857 apt-get: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6) #9 ERROR: process "/bin/bash -ol pipefail -c apt-get update && apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1" did not complete successfully: exit code: 1 Dockerfile:9 ------------------- 7 | COPY .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix 8 | RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d 9 | >>> RUN apt-get update && apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1 ------------------- ERROR: failed to solve: process "/bin/bash -ol pipefail -c apt-get update && apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1" did not complete successfully: exit code: 1 Error: Docker build failed
91 Replies
Project ID:
e7c663db-2958-40f5-8413-0118a353df39
@brody192 is there a channel or funnel that offers faster resolution when things like this comee up? This is a live app, with users. Also moving forward, I guess I should implement some form of redundancy. Does Railway have any specific protocols or preferred workflows for that?
don't ping Conductors or Team Members #πο½readme 5)
This is a community driven help channel, if u need faster resolution u should change to the Pro Plan
Ok
Then the Team can help u
I'm on the pro plan
It says ur on the hobby plan on discord
yea I see
I mean't a paid plan
will see if I can upgrade
if the price difference isn't crazy
Upload the full logs please, you can use this bookmarklet for it
https://bookmarklets.up.railway.app/log-downloader/
U will get access to Email Support with a team member
and imo, if u want to be more 'secure', build your own Dockerfile instead of using Nixpacks
for me, Dockerfile has more consistency, since i can test locally and I know for sure it will work on railway (you can test locally with nixpacks too, but i can't rely on it that much if i have a lot of settings/configs it doesn't detect by default)
I upgraded to pro plan (apparently two times which I guess I'll figure out later)
I have the same issue using Nixpacks
And in terms of email support is that faster? Didn't particularly answer the question
And now that I'm on like a double pro plan or something, does that mean I can get answers without me being treated like the jerk for asking? Trying to understand the rules exactly
this is a community-driven discord, we may not be able to help u or even ur thread may go without answers, the Team for sure can help you
have you tried building the dockerfile urself instead of using nixpacks? do it produce the same error?
I just sent them an email, I'll let you know when they answer
Thanks @jclaveau I emailed them as well. Will do the same
Also the enterprise plan does include support SLA if you are interested in/require even faster team support.
So we should pay more for Railway to fix their process? Seems odd to me
Seems odd to me that I paid more, and also didn't help
Sorry, I'm not familiar with your issue and don't undestand your question. I'm simply mentioning that Railway does offer plans with faster support in case you needed it.
Where is this faster support @jonbeau ? Did you use it before?
I have the plans you're saying get faster support
I am not getting faster support
In fact, when I send the email. . . I get the same email that non pro plans members get
It's the same email
before someone says it
Hey all, apart from the paid/hobby discussion. I'm also facing this issue on builds
is there a resolution?
@ryan_the_temp solution for now is to upgrade to the pro plan so you can "get faster support" and then not actually get faster support
Hey, wdym by build issues? is it the same error as this one?
And still have the same error
Wouldn't recommend lol
Did u try what i said?
your own dockerfile?
Did I try to spend time building my own dockerfile to circumvent an error that 3-4 people are also facing here?
No, I didn't try that
The faster support I'm reffering to is the support SLA offered on the enterprise plan. A service level agreement means, for example only, that Railway would agree to respond to your ticket in x amount of time and resolve it in y. I haven't used it, I'm only on the hobby plan.
I think I have the same error:
@medim should I rebuild everyone's dockerfile to circumvent the issue?
Seems like it'd be easier just to fix it globally
Could u please open a thread and paste ur entire build log there?
You can use this bookmarklet for that: https://bookmarklets.up.railway.app/log-downloader/
Also describe ur problem
@ryan_the_temp literally has the exact same problem
No, he doesn't
As I said, this help section is mostly community driven
His log:
0.329 apt-get: /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.36' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
My log:
0.479 apt-get: /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.36' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
and ok
slightly different but extremely likely related problemthe log contains all my env var names. I don't think I want that public. I can just past the relevant section
@coffeecup glibc 2.36 not found
My man!!
@brody192 here, day is saved
And sorry for pinging again but it was to celebrate
But its basically same as @itsjnewt said:
the upgrade to pro wasn't necessary to get support for a platform issue, there was just no one around to escalate this to a team member
Well, just doing whatever it took
this isn't the first thread about the missing glibc 2.36, jr already knows about it and was already looking into a solution, but a temp solution to get your build to work right now would be to pin the nixpacks version to the previous version.
in a railway.toml set the nixpacks version to 1.15.0 (the previous nixpacks version)
https://docs.railway.app/deploy/config-as-code#nixpacks-version
Will give that a shot. Thanks so much
I have the team plan
βοΈ Thanks, I'll try that
Team Plan = Pro Plan
I wonder why the issue just started happing, I wander if its sporadic because nothing else really changed other than application code in my case
plan doesn't matter in cases where the issue is with the platform
the global nix archive version was updated this changed a whole lot of packages, probably should have been an announcement looking back at things now
hmm, I see
well, thanks for the workaround.
nix packs build works locally
yeah, I think upstream changes like need better communication, or at least rolled out progressively
when jr has a fix, I'd come back and ask y'all to spin up a test environment using the latest nixpacks version so prod isn't effected
you are using nixpacks 1.13.0 locally, the issue lies with nixpacks 1.16.0
Agree that we should have communicated this better (we did mention that the default NodeJS would be 18 in a few changelogs back). But failed to mention that other packages would be affected. The issue lies with Python and glibc. At least with all the issues I've seen, that is the common denominator.
However, I think we just need to add this as a test case so it doesn't happen again in the future. The Nixpacks CI should have caught this. If one of you has a simple public repo where this issue can be reproduced that would be great so that we can use it as a test case
Please downgrade versions for now. A fix should be available early next week
where did @medim go? I thought I was the jerk for asking this question. . . hmmmπ€
? When did i called you a jerk?
I said to not ping Team and or Conductors
hey hey it's all good
Glad the team got back to it and was able to help you out
Next time remember, its a community driven help channel and the problem u had was with the platform, something that we can't do anything about it.
And don't be so salty, just tried to help, really.
I'm just picking. I appreciate the help π
I have no public repo but my service is a simple Directus app installed from the cli. Should I share my package.json and nixpacks.toml here? https://github.com/railwayapp/nixpacks/issues/950
GitHub
Issue while creating Docker image for Django application with lates...
Is there an existing issue for this? I have searched the existing issues Describe the bug Facing issue while creating a docker image for django application with the following error: [stage-0 6/8] R...
There's a Directus template that I created, you can try it and if you need help with it just DM me
yes that would be great please
My Directus app is versionned in a monorepo but if you spent some time on the Dockerfile i'd love to give a look to it, espacially the way you handled Directus/Dependencies upgrades.
Oh you use it in a monorepo, my template is pretty simple, just to get Directus running easily https://railway.app/template/2fy758
Its basically plain Directus without any extension, I doubt it will help you in any way but if it does...
Theres no Dockerfile, just some railway config files
Done
Just because u posted ur Directus .toml and package.json ,keep in mind these newer Directus version also need 'build-essential' and 'glibc-source' to run
some issue related to vm2 being deprecated and changed to isolated-vm
(tried to find the discussion with a mod in the directus discord but the automod removed the thread)
I've had this same problem since a few days ago:
I need to use playwright install and playwright install-deps to run my code, but it is currently giving this error (before the installation worked normally)!
There's some solution?
Rollback nixpacks version
It's not the first time this is reported
https://discord.com/channels/713503345364697088/1154348641809608764/1154440076290424832
How can I do this? Should I download a file with the commands, or execute them via subprocess with Python?
the message medim linked tells you what to do, and the link within that message gives you an example
Brody, this toml is correctly configured to install the "1.15.0" nixpacks version?
Code:
okay looks good, what version of nixpacks is railway using to run your build now?
It's the most recent.
what version
Nixpacks v1.16.0
and where do you have that railway.toml located?
I took a look and it seems that in version
v1.14.0
of Nixpacks everything was fine.
I put it in the same place as the bad main.py
that runs my Discord bot.screenshot of the folder structure please?
the folder structure in github please
and thats the root directory?
Yes. I think'll work now. Couse is already downloading the
1.14.0
version of Nixpacksokay good
Yeah.. it worked! Thank you very much for your immediate help!
no problem!
hey, I'm facing the same problem rn
On build, my version in
nixpacks.toml
doesn't get recognized
it still sues 1.16.0Could you share your folder structure and the toml file?
the output of
tree -L 2
from git repo parent folder.
this is nixpacks.toml
The Dockerfile is a newer addition, it is what I'm using rn to deploy π
railways json - at first didn't use it at all, then I throught it might be the issue of version not getting fetched up, but the version that still didn't work properly is pretty much your default one:
now that i think about it -maybe "$schema" is the culprit? i dunnoI am having this same issue
The nixpacks version should be in the
railway.toml
file
ah, so in my case it's
railway.json
, ye, indeed, I guess confused two tabs with docs when I was looking at them and misunderstood where I should put the version, ty!
I am quite deep into Dockerfile already, but will be sure to use it this way next time π
yeah it is a bit confusing, we know. Are looking to improve this whole experience soon!