Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fdbcli segmentation fault in container when FDB_TLS_VERIFY_PEERS envvar is defined #11962

Open
czephyr opened this issue Feb 20, 2025 · 0 comments

Comments

@czephyr
Copy link

czephyr commented Feb 20, 2025

Hello.

I'm bumping into this when using fdbcli inside my podman container:

bash-5.1# fdbcli
Using cluster file `/etc/foundationdb/fdb.cluster'.
SIGNAL: Segmentation fault (11)
Trace: addr2line -e fdbcli.debug -p -C -f -i 0x7f622e19a6f0 0x179043a 0x17925c8 0x19d103e
Segmentation fault

My setup has TLS and I want to define these vars inside my container.

-FDB_TLS_VERIFY_PEERS
-FDB_TLS_CA_FILE
-FDB_TLS_KEY_FILE
-FDB_TLS_CERTIFICATE_FILE
-FDB_CLUSTER_FILE

These settings are also defined in the [fdbserver] config (and the values are the same) but I want to be able to run fdbcli without having to add the flags when inside the container.

It looks like this happens when I mount the container and the podman --envfile contains the env variable FDB_TLS_VERIFY_PEERS.

When I mount an envfile that doesn't contain that var fdbcli works.
When I mount an envfile that doesn't contain that var and I later export it after startup it works.

It might be something I'm overlooking, maybe. Image is foundationdb:7.3.59.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant