Segfault when connecting to db from docker container.

[Ayman250]

Having an issue connecting to DB through a docker container. This happens only in Docker, it works fine locally on my machine.

Valgrind dump shows:

==6704== Thread 26 DbLoop:
==6704== Invalid read of size 8
==6704==    at 0x4B046F7: SSL_get_peer_certificate (in /usr/lib/x86_64-linux-gnu/libssl.so.1.1)
==6704==    by 0x48F461E: ??? (in /usr/lib/x86_64-linux-gnu/libpq.so.5.12)
==6704==    by 0x48DEEF7: PQconnectPoll (in /usr/lib/x86_64-linux-gnu/libpq.so.5.12)
==6704==    by 0x33B477: drogon::orm::PgConnection::pgPoll() (in /usr/chatbot/build/chatbot)
==6704==    by 0x80888F: trantor::Channel::handleEventSafely() (in /usr/chatbot/build/chatbot)
==6704==    by 0x7FD00F: trantor::EventLoop::loop() (in /usr/chatbot/build/chatbot)
==6704==    by 0x7FE839: trantor::EventLoopThread::loopFuncs() (in /usr/chatbot/build/chatbot)
==6704==    by 0x4F0EDE3: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==6704==    by 0x486C608: start_thread (pthread_create.c:477)
==6704==    by 0x52A3132: clone (clone.S:95)
==6704==  Address 0x1000001b7 is not stack'd, malloc'd or (recently) free'd

Anyone run into something similar?

[Ayman250]

Fixed by building my own image with newer version of ubuntu. I'm assuming there was some version mismatch somewhere with openssl or something. Not sure.