Lars Erdmann

Hi Mounir, I have recreated the whole thing and found out why veracrypt no longer worked even on the host system. When the 'veracrypt create (exfat)' in the docker container fails, a directory /dev/mapper/veracrypt1 remains on the host system, which should normally be removed. Fort the host system the solution is to run: cryptsetup close veracrypt1. But the question that remains with me is: Why does the creation of a Veracrypt volume in docker fail when the filetype is something other than fat (e.g....

Dear all, i have some issues with the creation of a container file per command line. My system as an up to date debian 12 with veracrypt-console-1.25.9-Debian-12-amd64.deb, exfat-fuse and exfat-utils installed and root rights. You can see my complete configuration on https://github.com/larserdmann/veracrypt-in-docker/blob/master/Dockerfile. In a console i can create and mount container with 'fat' filesystem just fine. example for container creation: veracrypt -t -v \ --create "test.vc" \ --size="5000M"...