@Kriss I haven’t tested this, but perhaps the ip command is trying to load a kernel module that is not allowed.
If you ensure any kernel modules are loaded on the host before trying to create the tunnel in the container that may fix it.
@Kriss I haven’t tested this, but perhaps the ip command is trying to load a kernel module that is not allowed.
If you ensure any kernel modules are loaded on the host before trying to create the tunnel in the container that may fix it.