Bug 10781

# creating container file works
dd if=/dev/urandom of=container_file bs=1M count=10
cryptsetup -y luksFormat container_file

cryptsetup --debug open container_file container
# cryptsetup 2.0.1 processing "cryptsetup --debug open container_file container"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device container_file.
# Trying to open and read device container_file with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device container_file.
# Crypto backend (OpenSSL 1.0.2n  7 Dec 2017) initialized in cryptsetup library version 2.0.1.
# Detected kernel Linux 4.15.0 i686.
# PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, parallel_threads 0.
# Reading LUKS header of size 1024 from device container_file
# Key length 32, device size 20480 sectors, header size 2050 sectors.
# Activating volume container using token -1.
# Interactive passphrase entry requested.
Enter passphrase for container_file:
# Activating volume container [keyslot -1] using passphrase.
# dm version   [ opencount flush ]   [16384] (*1)
# dm versions   [ opencount flush ]   [16384] (*1)
# Detected dm-ioctl version 4.37.0.
# Device-mapper backend running with UDEV support disabled.
# dm status container  [ opencount flush ]   [16384] (*1)
Segmentation fault

dmesg
cryptsetup[150]: segfault at bf779fc4 ip b7eb6cf7 sp bf779fc8 error 6 in libdevmapper.so.1.02[b7e84000+44000]

I changed original supplied version 2.0.0 to 2.0.1 but it´s still not working.