FFMPEG issues despite recommendations
I'm having a few issues getting FFMPEG started.
Firstly, I found that the package could not be found. There is a fix here that fixes that error by changing the nixpacks.toml:
[phases.setup]
aptPkgs = ["...", "ffmpeg"]
however, I'm faced with a new error: ffmpeg: /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'm seeing some suggestions to maybe lower my build version like this:
[build]
nixpacksVersion = "1.15.0"
`
But still having no results.
Built with FastAPI, python, and FFMPEG.
Service ID: 8b2dbccb-8e08-4422-a6da-0b275b5f66fc12 Replies
Project ID:
8b2dbccb-8e08-4422-a6da-0b275b5f66fc
ffmpeg can be added to the app image using docker's multi-stage builds. It requires using Dockerfile but should actually work
Anywhere you can point me to setting something like that up? Don't really have experience with Docker.
But there's essentially no way to do this through Railway exclusively with build commands, etc?
probably not. maybe more experienced guys can help with that
take
python:3-bookworm
as base image and install ffmpeg into it with apt install ffmpeg
If you want me to I can try doing it@hammyg - first, the nixpacks version thing goes in a railway.toml file, not a nixpacks.toml file.
second, try adding this under your phases.setup
nixLibs = ['...', 'zlib']
Updated nixpacks.toml:
[phases.setup]
aptPkgs = ["...", "ffmpeg"]
nixLibs = ['...', 'zlib']
Created railway.toml to test as well:
[build]
nixpacksVersion = "1.15.0"
Still unfortunately left with the error:
ffmpeg: /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)
does the build table at the top of the build logs say it's running on nixpacks 1.15.0 now?
Thanks for responding, by the way. It does I believe:
and you still get a GLIBC_2.36 error?
can you try a build where you arent specifying the nixpacks version?
Oops, never mind. Looks like the version change did fix this issue, I'm sorry. Thank you for pointing out how to properly put a fixed version for railway.
It might be a worthwhile discussion to eventually have this work on the latest version, but the short fix is the version downgrade. Thanks for the help @Brody and @maddsua .