Closed DiamondShark closed 1 year ago
I can also confirm this, still happening on latest build.
Can confirm. Assumed it was a misconfiguration of some sorts on my end, but seems others have encountered this issue as well
Previous ubuntu was packaging vncpasswd into tigervnc-common, wich is installed by Dockerfile. (cf : https://manpages.ubuntu.com/manpages/focal/man1/tigervncpasswd.1.html)
But, since ubuntu 22.04LTS, vncpasswd is shipped by tigervnc-tools, wich is not currently installed by Dockerfile. (cf : https://manpages.ubuntu.com/manpages/jammy/man1/tigervncpasswd.1.html)
I am going to create a pull request to fix this.
@realies : it's kind of dangerous to use "FROM ubuntu:latest" into your Dockerfile because your build is dependant on when you build it. I think it would be more safe to explicitly set the base image you use.
Fixed here : https://github.com/gordon00/soulseek-docker/commit/fd16ed2668caea714c0fa1771dcf9efc594aeceb PR comming...
Thanks to @gordon00, this appears to be fixed now.
Hi! When I try to build from a docker-compose file, here's the error that I get:
soulseek | /init.sh: 14: vncpasswd: not found soulseek exited with code 127
Here's the sample of the docker compose file!