dockur
I fail to start the container up
Operating system
I am on Windows 11 (home edition), not Linux
Description
I start (for the first time, I just cloned the git repository).
docker run -it --rm --name windows -p 8006:8006 --device=/dev/kvm --device=/dev/net/tun --cap-add NET_ADMIN -v "${PWD:-.}/windows:/storage" --stop-timeout 120 dockurr/windows
And get a after a few minutes this error:
docker: Error response from daemon: error gathering device information while adding custom device "C": no such file or directory
Docker compose
$ cat compose.yml services: windows: image: dockurr/windows container_name: windows environment: VERSION: "11" USERNAME: "billy" PASSWORD: "goates" devices: - /dev/kvm - /dev/net/tun cap_add: - NET_ADMIN ports: - 8006:8006 - 3389:3389/tcp - 3389:3389/udp volumes: - ./windows:/storage restart: always stop_grace_period: 2m
Docker log
n/a
Screenshots (optional)
No response
@kroese - no, no change. But you had a good idea. The first attempts with "docker run" left an badly named directory behind: 'windows;C'/.
I tried docker-compose now, and while it configures a container, half assed (it shows up in the docker desktop app), it gives me repeated the same error message:
windows | ❯ Starting Windows for Docker v4.34...
windows | ❯ For support visit https://github.com/dockur/windows
windows | ❯ CPU: AMD Ryzen 5 7520U | RAM: 2/4 GB | DISK: 122 GB (v9fs) | KERNEL: 5.15.167.4-microsoft-standard-WSL2...
windows |
windows | ❯ ERROR: Your configured RAM_SIZE of 4 GB is too high for the 2.8 GB of memory available, please set a lower value.
windows exited with code 0
windows | ❯ CPU: AMD Ryzen 5 7520U | RAM: 2/4 GB | DISK: 122 GB (v9fs) | KERNEL: 5.15.167.4-microsoft-standard-WSL2...
windows |
windows | ❯ ERROR: Your configured RAM_SIZE of 4 GB is too high for the 2.8 GB of memory available, please set a lower value.
windows exited with code 0
I do not know what 2.8G versus 4G it is talking about. 4G is mentioned on the Dockerfile, but if I change it to 2GB the error stays the same. Perhaps somewhere in the WSL2 configuration is an error?
I just started anther docker image, first via GUI, then via command line - works just fine. (I only have two at the moment, but I think it is not docker itself)
Hello, Raspberry Pi 5 user here, and surprisingly I'm having similar issues. I got the RAM size issue first, now I've starting having a similar issue.
Here are my logs in case they may be useful (please let me know if I should open a new issue, I'd be happy to do so).
Hello, Raspberry Pi 5 user here, and surprisingly I'm having similar issues. I got the RAM size issue first, now I've starting having a similar issue.
Here are my logs in case they may be useful (please let me know if I should open a new issue, I'd be happy to do so).
hmmm ok, so I sorted out the issue with /dev/net/tun like this:
mkdir -p /dev/net
sudo mknod /dev/net/tun c 10 200
sudo chmod 600 /dev/net/tun
And for RAM I avoided running to many apps before starting the VM, and that way it would take the RAM available before other processes started using it up (I've only got 8GB RAM so it makes sense if I've got lots of stuff open etc.).
My quick research came from here (had to add sudo to the last few commands because of permission errors):
- https://www.google.com/search?as_q=&as_epq=error+gathering+device+information+while+adding+custom+device+%22%2Fdev%2Fnet%2Ftun%22&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=all&as_sitesearch=&as_occt=any&as_filetype=&tbs=
- https://github.com/qdm12/gluetun/discussions/1163