You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My server runs Ubuntu 18.04 and I'm having trouble getting my app (that uses go-sqlite) to run there.
First, I had to install a newer version of glibc:
$ ./sqlite-linux-repro
./sqlite-linux-repro: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./sqlite-linux-repro)
./sqlite-linux-repro: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./sqlite-linux-repro)
./sqlite-linux-repro: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./sqlite-linux-repro)
./sqlite-linux-repro: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./sqlite-linux-repro)
./sqlite-linux-repro: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.28' not found (required by ./sqlite-linux-repro)`
implies you built your application on a distro that is newer than 18.04, you app then requires a newer version of libc, but that the only version of libc available is too old. Instead build your application on Ubuntu 18.04 if you want to be sure it will run on 18.04. It'll probably also then run on newer versions of Ubuntu, since newer versions of libc should work fine too (but not the other way around, which is what you're hitting).
My server runs Ubuntu 18.04 and I'm having trouble getting my app (that uses go-sqlite) to run there.
First, I had to install a newer version of glibc:
And since doing that I've been getting a segfault
Here's a minimal reproduction: https://github.com/Teajey/sqlite-linux-repro
There's a Dockerfile that recreates the conditions:
There's no stderr output for some reason. But you can verify the segfault by checking the exit code:
Perhaps it's a problem with using these versions of Ubuntu and glibc together.
I'm unfortunately not clued-up enough to find the core dump file, let alone make sense of it.
Thanks for any help.
The text was updated successfully, but these errors were encountered: