Kroese

Closing because of no response.

I don't know what is causing that. It seems that on Synology this container does not run well. But I have not much motivation to figure out what is causing...

Closing because of no response

I never used KASM and dont know how it works, so I cannot provide an answer to this question Im afraid.

Can you add this to your compose file? ```yaml3 sysctls: - net.ipv4.ip_forward=1 ```

I do not think this is a general problem, but probably that Docker is just mis-configured on your system. Normally its not required to use sudo. When Googling for docker...

Then maybe the permissions on `/dev/kvm` are not allowing access for a normal user? What do you get when you run: ``` stat --format '%a' /dev/kvm ``` On my system...

Does it work when you add ``` privileged: true ``` To the compose file and run it without sudo?

If you can only run the container with the privileged flag, it is a sign of another problem that I would like to understand first instead of working around it...

What is your OS, kernel and Docker version?