Railway•15mo ago

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

Percy•15mo ago

Project ID: e7c663db-2958-40f5-8413-0118a353df39

John NewtonOP•15mo ago

@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?

Medim•15mo ago

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

John NewtonOP•15mo ago

Medim•15mo ago

Then the Team can help u

John NewtonOP•15mo ago

I'm on the pro plan

Medim•15mo ago

It says ur on the hobby plan on discord

John NewtonOP•15mo ago

yea I see I mean't a paid plan will see if I can upgrade if the price difference isn't crazy

Medim•15mo ago

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)

John NewtonOP•15mo ago

I upgraded to pro plan (apparently two times which I guess I'll figure out later)

John NewtonOP•15mo ago

build_logs_ontro_169...

Jean•15mo ago

I have the same issue using Nixpacks

John NewtonOP•15mo ago

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

Medim•15mo ago

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?

Jean•15mo ago

I just sent them an email, I'll let you know when they answer

John NewtonOP•15mo ago

Thanks @jclaveau I emailed them as well. Will do the same

jonbeau•15mo ago

Also the enterprise plan does include support SLA if you are interested in/require even faster team support.

Jean•15mo ago

So we should pay more for Railway to fix their process? Seems odd to me

John NewtonOP•15mo ago

Seems odd to me that I paid more, and also didn't help

jonbeau•15mo ago

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.

John NewtonOP•15mo ago

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

John NewtonOP•15mo ago

It's the same email before someone says it

Ryan The Temp•15mo ago

Hey all, apart from the paid/hobby discussion. I'm also facing this issue on builds is there a resolution?

John NewtonOP•15mo ago

@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

Medim•15mo ago

Hey, wdym by build issues? is it the same error as this one?

John NewtonOP•15mo ago

And still have the same error Wouldn't recommend lol

Medim•15mo ago

Did u try what i said? your own dockerfile?

John NewtonOP•15mo ago

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

jonbeau•15mo ago

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.

Ryan The Temp•15mo ago

I think I have the same error:

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)

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)

John NewtonOP•15mo ago

@medim should I rebuild everyone's dockerfile to circumvent the issue? Seems like it'd be easier just to fix it globally

Medim•15mo ago

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

John NewtonOP•15mo ago

@ryan_the_temp literally has the exact same problem

Medim•15mo ago

No, he doesn't As I said, this help section is mostly community driven

John NewtonOP•15mo ago

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 problem

Ryan The Temp•15mo ago

the log contains all my env var names. I don't think I want that public. I can just past the relevant section

Brody•15mo ago

@coffeecup glibc 2.36 not found

John NewtonOP•15mo ago

My man!! @brody192 here, day is saved And sorry for pinging again but it was to celebrate

Ryan The Temp•15mo ago

But its basically same as @itsjnewt said:

#8 28.61 44 store paths deleted, 259.64 MiB freed

#8 DONE 28.8s

#9 [stage-0  5/12] 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 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)
#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
-----
> [stage-0  5/12] 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:
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)
-----

#8 28.61 44 store paths deleted, 259.64 MiB freed

#8 DONE 28.8s

#9 [stage-0  5/12] 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 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)
#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
-----
> [stage-0  5/12] 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:
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)
-----

Brody•15mo ago

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

John NewtonOP•15mo ago

Well, just doing whatever it took

Brody•15mo ago

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

John NewtonOP•15mo ago

Will give that a shot. Thanks so much

Jean•15mo ago

I have the team plan

Ryan The Temp•15mo ago

☝️ Thanks, I'll try that

Medim•15mo ago

Team Plan = Pro Plan

Ryan The Temp•15mo ago

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

Brody•15mo ago

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

Ryan The Temp•15mo ago

hmm, I see well, thanks for the workaround.

Jean•15mo ago

message.txt

Jean•15mo ago

nix packs build works locally

Ryan The Temp•15mo ago

yeah, I think upstream changes like need better communication, or at least rolled out progressively

Brody•15mo ago

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

jr•15mo ago

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

John NewtonOP•15mo ago

where did @medim go? I thought I was the jerk for asking this question. . . hmmm🤔

Medim•15mo ago

? When did i called you a jerk? I said to not ping Team and or Conductors

Brody•15mo ago

hey hey it's all good

Medim•15mo ago

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.

John NewtonOP•15mo ago

I'm just picking. I appreciate the help 😁

Jean•15mo ago

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...

Medim•15mo ago

There's a Directus template that I created, you can try it and if you need help with it just DM me

jr•15mo ago

yes that would be great please

Jean•15mo ago

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.

Medim•15mo ago

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

Jean•15mo ago

Done

Medim•15mo ago

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)

alyson•15mo ago

I've had this same problem since a few days ago:

/opt/venv/lib/python3.10/site-packages/playwright/driver/node: /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)

/opt/venv/lib/python3.10/site-packages/playwright/driver/node: /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)

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?

Medim•15mo ago

Rollback nixpacks version It's not the first time this is reported https://discord.com/channels/713503345364697088/1154348641809608764/1154440076290424832

alyson•15mo ago

How can I do this? Should I download a file with the commands, or execute them via subprocess with Python?

Brody•15mo ago

the message medim linked tells you what to do, and the link within that message gives you an example

alyson•15mo ago

Brody, this toml is correctly configured to install the "1.15.0" nixpacks version? Code:

[build]
nixpacksVersion = "1.15.0"
builder = "NIXPACKS"

[deploy]
numReplicas = 1
restartPolicyType = "ON_FAILURE"
restartPolicyMaxRetries = 10

[build]
nixpacksVersion = "1.15.0"
builder = "NIXPACKS"

[deploy]
numReplicas = 1
restartPolicyType = "ON_FAILURE"
restartPolicyMaxRetries = 10

Brody•15mo ago

okay looks good, what version of nixpacks is railway using to run your build now?

alyson•15mo ago

It's the most recent.

Brody•15mo ago

what version

alyson•15mo ago

Nixpacks v1.16.0

Brody•15mo ago

and where do you have that railway.toml located?

alyson•15mo ago

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.

Brody•15mo ago

screenshot of the folder structure please? the folder structure in github please and thats the root directory?

alyson•15mo ago

Yes. I think'll work now. Couse is already downloading the 1.14.0 version of Nixpacks

Brody•15mo ago

okay good

alyson•15mo ago

Yeah.. it worked! Thank you very much for your immediate help!

Brody•15mo ago

no problem!

alexbalandi•15mo ago

hey, I'm facing the same problem rn On build, my version in nixpacks.toml doesn't get recognized it still sues 1.16.0

Faraz•15mo ago

Could you share your folder structure and the toml file?

alexbalandi•15mo ago

(data_science) [alexbalandi@alexbalandi linus_kannadb]$ tree -L 2
.
├── commit.sh
├── config
│   ├── __init__.py
│   ├── settings
│   ├── urls.py
│   └── wsgi.py
├── CONTRIBUTORS.txt
├── Dockerfile
├── docs
│   ├── conf.py
│   ├── deploy.rst
│   ├── docker_ec2.rst
│   ├── index.rst
│   ├── __init__.py
│   ├── install.rst
│   ├── make.bat
│   └── Makefile
├── LICENSE
├── linus
│   ├── conftest.py
│   ├── contrib
│   ├── feh
│   ├── __init__.py
│   ├── media
│   ├── static
│   ├── templates
│   ├── users
│   └── workspace.code-workspace
├── locale
│   └── README.rst
├── manage.py
├── merge_production_dotenvs_in_dotenv.py
├── nixpacks.toml
├── Procfile
├── pytest.ini
├── railway.json
├── README.rst
├── requirements
│   ├── base.txt
│   ├── local.txt
│   └── production.txt
├── requirements.txt
├── runtime.txt
├── setup.cfg
├── update.txt
└── utility
    ├── install_os_dependencies.sh
    ├── install_python_dependencies.sh
    ├── requirements-jessie.apt
    ├── requirements-stretch.apt
    ├── requirements-trusty.apt
    └── requirements-xenial.apt

(data_science) [alexbalandi@alexbalandi linus_kannadb]$ tree -L 2
.
├── commit.sh
├── config
│   ├── __init__.py
│   ├── settings
│   ├── urls.py
│   └── wsgi.py
├── CONTRIBUTORS.txt
├── Dockerfile
├── docs
│   ├── conf.py
│   ├── deploy.rst
│   ├── docker_ec2.rst
│   ├── index.rst
│   ├── __init__.py
│   ├── install.rst
│   ├── make.bat
│   └── Makefile
├── LICENSE
├── linus
│   ├── conftest.py
│   ├── contrib
│   ├── feh
│   ├── __init__.py
│   ├── media
│   ├── static
│   ├── templates
│   ├── users
│   └── workspace.code-workspace
├── locale
│   └── README.rst
├── manage.py
├── merge_production_dotenvs_in_dotenv.py
├── nixpacks.toml
├── Procfile
├── pytest.ini
├── railway.json
├── README.rst
├── requirements
│   ├── base.txt
│   ├── local.txt
│   └── production.txt
├── requirements.txt
├── runtime.txt
├── setup.cfg
├── update.txt
└── utility
    ├── install_os_dependencies.sh
    ├── install_python_dependencies.sh
    ├── requirements-jessie.apt
    ├── requirements-stretch.apt
    ├── requirements-trusty.apt
    └── requirements-xenial.apt

the output of tree -L 2 from git repo parent folder.

[build]
nixpacksVersion = "1.14.0"
[phases.setup]
#nixPkgs = ["...", "glibc", "curl", "openssl"]
aptPkgs = ["...", "libcurl4-openssl-dev", "libssl-dev"]   # Install the wget package with apt-get

[build]
nixpacksVersion = "1.14.0"
[phases.setup]
#nixPkgs = ["...", "glibc", "curl", "openssl"]
aptPkgs = ["...", "libcurl4-openssl-dev", "libssl-dev"]   # Install the wget package with apt-get

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:

{
    "$schema": "https://railway.app/railway.schema.json",
    "build": {
      "builder": "NIXPACKS",
      "nixpacksConfigPath": "nixpacks.toml"
    },
    "deploy": {
      "numReplicas": 1,
      "sleepApplication": false,
      "restartPolicyType": "ON_FAILURE",
      "restartPolicyMaxRetries": 10
    }
  }

{
    "$schema": "https://railway.app/railway.schema.json",
    "build": {
      "builder": "NIXPACKS",
      "nixpacksConfigPath": "nixpacks.toml"
    },
    "deploy": {
      "numReplicas": 1,
      "sleepApplication": false,
      "restartPolicyType": "ON_FAILURE",
      "restartPolicyMaxRetries": 10
    }
  }

now that i think about it -maybe "$schema" is the culprit? i dunno

Josh•15mo ago

I am having this same issue

jr•15mo ago

The nixpacks version should be in the railway.toml file

[build]
nixpacksVersion = "1.14.0"

[build]
nixpacksVersion = "1.14.0"

alexbalandi•15mo ago

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 😅

jr•15mo ago

yeah it is a bit confusing, we know. Are looking to improve this whole experience soon!

Gaming

Programming

apt-get update failing due to a missing GLIBC_2.36 version