docker run command fails to run on Project64 dockerfile

[j0lol]

System: Arch Linux
Output:

$ docker run -it --rm \
> -v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native -e PULSE_SERVER=unix:/run/user/1000/pulse/native \
> -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY \
> -v ~/Games/N64:/home/wine/.wine/drive_c/N64 \
> -v ~/.config/project64/config:/home/wine/.wine/drive_c/Project64/Config \
> -v ~/.config/project64/save:/home/wine/.wine/drive_c/Project64/Save \
> --device /dev/input/js0 \
> jbergknoff/project64
docker: unknown server OS: .
See 'docker run --help'.

[j0lol]

whoops wrong repo sorry (also it double posted for some reason?) :p 

[j0lol]

edit: nvm i thought the project64 dockerfile was on a different repo im dumb sorry

[jbergknoff]

docker: unknown server OS: .

Pretty cryptic :) What version of Docker are you running? Are you able to run other containers?

Based on googling that error message (e.g. this), I'm guessing it has to do with --device /dev/input/js0. Do you actually have a joystick at /dev/input/js0? Does the container run if you omit that option?

[j0lol]

I haven't tried running other containers since I've never really used docker on this system :p

What version

$ docker version
Client:
 Version:           19.03.12-ce

Do you actually have a joystick at /dev/input/js0?

$ cat /dev/input/js0
cat: /dev/input/js0: No such file or directory

I don't have any joysticks plugged in right now! I'll try plugging one in.
(that didnt help)

Removed the device flag:

$ docker run -it --rm \
> -v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native -e PULSE_SERVER=unix:/run/user/1000/pulse/native \
> -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY \
> -v ~/Games/N64:/home/wine/.wine/drive_c/N64 \
> -v ~/.config/project64/config:/home/wine/.wine/drive_c/Project64/Config \
> -v ~/.config/project64/save:/home/wine/.wine/drive_c/Project64/Save \
> jbergknoff/project64
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
$ sudo !!
sudo docker run -it --rm -v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native -e PULSE_SERVER=unix:/run/user/1000/pulse/native -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY -v ~/Games/N64:/home/wine/.wine/drive_c/N64 -v ~/.config/project64/config:/home/wine/.wine/drive_c/Project64/Config -v ~/.config/project64/save:/home/wine/.wine/drive_c/Project64/Save jbergknoff/project64
Unable to find image 'jbergknoff/project64:latest' locally
docker: Error response from daemon: manifest for jbergknoff/project64:latest not found: manifest unknown: manifest unknown.
See 'docker run --help'.

not sure whats going on, im not too familiar with docker? i ran the docker pull command from your site. (also dunno why i need sudo for docker, will look that up in a minute.)
edit: looked that up, guess ill reboot quick

[jbergknoff]

Thanks for the details.

• It looks like removing the --device fixed the original error.

• Docker requires sudo or (equivalently) for the user to be in the docker group. Docs on that here: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user.

• jbergknoff/project64:latest not found

  This is a bug in the readme (which I'll fix). Try specifying the tag like this: docker run ... jbergknoff/project64:v2.4.0-1225-gb9dac46. The list of tags is here: https://hub.docker.com/r/jbergknoff/project64/tags, and that one is the latest that's been built.

[j0lol]

Thanks for the help!
I'll reboot to fix that permissions error soon, but for now i'll just run it like this.

$ sudo !!
sudo docker run -it --rm -v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native -e PULSE_SERVER=unix:/run/user/1000/pulse/native -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY -v ~/Games/N64:/home/wine/.wine/drive_c/N64 -v ~/.config/project64/config:/home/wine/.wine/drive_c/Project64/Config -v ~/.config/project64/save:/home/wine/.wine/drive_c/Project64/Save jbergknoff/project64/project64:v2.4.0-1225-gb9dac46
[sudo] password for jo: 
Unable to find image 'jbergknoff/project64/project64:v2.4.0-1225-gb9dac46' locally
docker: Error response from daemon: pull access denied for jbergknoff/project64/project64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

Not sure why its throwing this error? I did pull the same version (and i ran the pull again just to be sure and it did the same thing)

[jbergknoff]

Looks like it's referencing jbergknoff/project64/project64:v2.4.0-1225-gb9dac46 (one extra project64). Should be jbergknoff/project64:v2.4.0-1225-gb9dac46.

[j0lol]

oh thats my fault! whoops

[j0lol]

alright, it seems to be running? doesnt seem to make a window though.
command:

docker run -it --rm \
	-v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native -e PULSE_SERVER=unix:/run/user/1000/pulse/native \
	-v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY \
	-v ~/Games/N64:/home/wine/.wine/drive_c/N64 \
	-v ~/.config/project64/config:/home/wine/.wine/drive_c/Project64/Config \
	-v ~/.config/project64/save:/home/wine/.wine/drive_c/Project64/Save \
	-e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e PULSE_SERVER=unix:/run/user/1000/pulse/native -v $XDG_RUNTIME_DIR/pulse/native:/run/user/1000/pulse/native \
    jbergknoff/project64:v2.4.0-1225-gb9dac46

error:

0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0009:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.

sorry to keep bothering you :p

[jbergknoff]

No problem. Is it possible there's no X server running? Are you using Wayland?

[j0lol]

nope :) using X

[jbergknoff]

Hm, I'm not sure what the issue is, then. I'd make sure there's a $DISPLAY environment variable set in the shell from which you're running Docker. -e DISPLAY is passing in that variable from the parent shell, and it looks like maybe it's missing in the container. You could also -e DISPLAY=:0 explicitly (if that's the right display). Please let me know if you have any luck with that.