Using SoftHSM2 from host with EJBCA and SignServer (glibc version mismatch) #978
-
|
Hi, I’m setting up EJBCA Community and SignServer Community to use SoftHSM2 installed on the host, instead of installing SoftHSM inside each Docker container. Here’s my environment setup:
Both containers define:
I cant list slots from EJBCA ui, instead i have this in the logs:
❓Question What’s the recommended approach here? Should I install SoftHSM inside each container so it matches the container’s glibc version? Or is there a recommended way to build a version of libsofthsm2.so that’s compatible with older glibc (e.g., 2.28–2.34) so it can be shared safely between containers? Any advice or examples from similar setups (modern Ubuntu host + RHEL/AlmaLinux-based containers) would be very helpful. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
There are many different approaches you can take. You can build libsofthsm so it's compatible with the container version of glibc, maybe that's the easiest. |
Beta Was this translation helpful? Give feedback.
There are many different approaches you can take. You can build libsofthsm so it's compatible with the container version of glibc, maybe that's the easiest.
Next release of EJBCA I think will use an updated container base as well.