segfault of binary release after upgrade from debian bullseye to bookworm #1561
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Hi, I run vikunja api in a debian based container and I get a segfault after upgrading my container from bullseye to bookworm.
My dockerfile:
I use PostgreSQL 15 as database.
Thanks!
Vikunja Frontend Version
0.20.5
Vikunja API Version
0.20.4
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
What kind of container? Did you build it yourself?
docker container. Yes I build myself.
My configuration looks like :
I noticed changing sslmode to
disable
doesn't trigger the bug. So I guess it's a bug in lib/pq related to sslmode. But I wonder why this occur on a bookworm container and not on bullseye since the vikunja binary the same and is statically built and should not depend on container environment.Can you share your docker run config / dockerfile?
The error message sounds like the built binary still depends on system libraries or old binary artifacts which are not present after the upgrade. The SQL part of Vikunja still requires those.
Why are you building your own docker images instead of using the official ones?