When using this library for shared memory communication in docker, I often encounter the following error and then crash

[Createrinfuture]

When using this library for shared memory communication in docker, I often encounter the following error and then crash

[elBoberido]

Are the applications communicating across docker instances when this happens?

Unfortunately, the log messages are not that helpful. Can you run your applications with the log level set to debug?
You can use iox::log::Logger::init(iox::log::logLevelFromEnvOr(iox::log::LogLevel::INFO)); by default and set the log level with the IOX_LOG_LEVEL environment variable. See also https://github.com/eclipse-iceoryx/iceoryx/blob/master/doc/design/logging.md#environment-variables.

Can you create a backtrace from a crashed application with this command

gdb --batch \
   --ex "shell printf '\n\033[33m#### Local Variables ####\033[m\n'"  --ex "info locals" \
   --ex "shell printf '\n\033[33m#### Threads ####\033[m\n'"          --ex "info threads" \
   --ex "shell printf '\n\033[33m#### Shared Libraries ####\033[m\n'" --ex "info sharedlibrary" \
   --ex "shell printf '\n\033[33m#### Stack Frame ####\033[m\n'"      --ex "info frame" \
   --ex "shell printf '\n\033[33m#### Register ####\033[m\n'"         --ex "info register" \
   --ex "shell printf '\n\033[33m#### Backtrace ####\033[m'"          --ex "thread apply all bt" \
   --core coreDumpFile binaryFile

With coreDumpFile the path to the actual core dump file and binaryFile the path to the crashed binary