[GH-ISSUE #836] Installation from client fails, docker containers do not build/run on OpenVZ VPS #216

New issue

Closed

opened 2026-10-13 20:15:37 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:15:37 +00:00

Owner

Originally created by @pbtsrc on GitHub (May 30, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/836

Installation from client fails with
Error code: 202. Server error: Docker container missing

docker build --no-cache --pull -t amnezia-awg /opt/amnezia/amnezia-awg
fails. Probably the same as in #817

docker build --network=host --no-cache --pull -t amnezia-awg /opt/amnezia/amnezia-awg
builds ok, but

docker run -d --log-driver none --restart always --privileged --cap-add=NET_ADMIN --cap-add=SYS_MODULE -p 12345:12345/udp -v /lib/modules:/lib/modules --sysctl="net.ipv4.conf.all.src_valid_mark=1" --name amnezia-awg amnezia-awg
fails with
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: resulting devices cgroup doesn't match target mode: unknown.

Originally created by @pbtsrc on GitHub (May 30, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/836 Installation from client fails with Error code: 202. Server error: Docker container missing docker build --no-cache --pull -t amnezia-awg /opt/amnezia/amnezia-awg fails. Probably the same as in #817 docker build --network=host --no-cache --pull -t amnezia-awg /opt/amnezia/amnezia-awg builds ok, but docker run -d --log-driver none --restart always --privileged --cap-add=NET_ADMIN --cap-add=SYS_MODULE -p 12345:12345/udp -v /lib/modules:/lib/modules --sysctl="net.ipv4.conf.all.src_valid_mark=1" --name amnezia-awg amnezia-awg fails with docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: resulting devices cgroup doesn't match target mode: unknown.

bsakaguchi closed this issue

2026-10-13 20:15:38 +00:00

bsakaguchi commented

2026-10-13 20:15:39 +00:00

Author

Owner

@sevbear commented on GitHub (May 30, 2024):

I encountered the same problem.

@sevbear commented on GitHub (May 30, 2024): I encountered the same problem.

bsakaguchi commented

2026-10-13 20:15:39 +00:00

Author

Owner

@chibuk commented on GitHub (May 31, 2024):

I encountered the same problem. Ubuntu Server 22.04.4 LTS

@chibuk commented on GitHub (May 31, 2024): I encountered the same problem. Ubuntu Server 22.04.4 LTS

bsakaguchi commented

2026-10-13 20:15:40 +00:00

Author

Owner

@RA1ALG commented on GitHub (Jun 1, 2024):

how to solve the problem?

@RA1ALG commented on GitHub (Jun 1, 2024): how to solve the problem?

bsakaguchi commented

2026-10-13 20:15:40 +00:00

Author

Owner

@pokamest commented on GitHub (Jun 11, 2024):

OpenVZ is not supported by Amnezia, the issue is in the --privileged --cap-add=NET_ADMIN args, which is not supported by Docker on OpenVZ virtualization, it requires full virtualization to enable these capabilities.

OpenVZ is not considered full virtualization because it uses container-based virtualization. This means it shares the host system's kernel with isolated containers, unlike full virtualization, which emulates an entire hardware system allowing multiple operating systems to run independently.

KVM (Kernel-based Virtual Machine) is a type of full virtualization, as it allows multiple operating systems to run unmodified on standard x86 hardware by using hardware virtualization extensions. Unlike OpenVZ, KVM provides each virtual machine with its own isolated kernel, making it suitable for running diverse operating systems and environments with greater flexibility and isolation.

@pokamest commented on GitHub (Jun 11, 2024): OpenVZ is not supported by Amnezia, the issue is in the `--privileged --cap-add=NET_ADMIN` args, which is not supported by Docker on OpenVZ virtualization, it requires full virtualization to enable these capabilities. OpenVZ is not considered full virtualization because it uses container-based virtualization. This means it shares the host system's kernel with isolated containers, unlike full virtualization, which emulates an entire hardware system allowing multiple operating systems to run independently. KVM (Kernel-based Virtual Machine) is a type of full virtualization, as it allows multiple operating systems to run unmodified on standard x86 hardware by using hardware virtualization extensions. Unlike OpenVZ, KVM provides each virtual machine with its own isolated kernel, making it suitable for running diverse operating systems and environments with greater flexibility and isolation.

bsakaguchi commented

2026-10-13 20:15:40 +00:00

Author

Owner

@RA1ALG commented on GitHub (Jun 14, 2024):

I'm using vm.nuxt.cloud, on KVM. A week earlier everything was working fine. The payment ended and I re-registered. After which the installation fails with the specified error.

@RA1ALG commented on GitHub (Jun 14, 2024): I'm using vm.nuxt.cloud, on KVM. A week earlier everything was working fine. The payment ended and I re-registered. After which the installation fails with the specified error.

bsakaguchi referenced this issue

2026-10-13 20:46:43 +00:00

[PR #216] [MERGED] Merge master to dev #1676