Console version in Docker

VMProtect
1

Hi,

I’m trying to run the Linux version of VMProtect (console version) inside a Docker container (part of automated build environment). The VMProtect process is terminated by the system and only reports “killed” / exits unexpectedly.

Is running VMProtect inside Docker officially supported? Are there any known requirements or limitations related to Docker security restrictions, seccomp, ptrace, memory mapping, namespaces, or required capabilities that could cause VMProtect to be terminated?

If Docker is supported, are there any specific container options or capabilities that should be enabled?

Thanks

2

Try to check “docker logs …”

3

I assume this means that Docker is officially supported by VMProtect, which doesn’t rely on things like systemd and ptrace, and that the issue is likely related to some missing dependency or container configuration on our side?

In cases like this Docker logs usually only contain the basic information that the process was terminated by the kernel.