-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New issue since refreshing container #93
Comments
@VinneyUK, how do you start the container? |
its within a stack in portainer. |
To be able to help, I need to reproduce your issue. How does Portainer start the container? |
|
@realies does that help? |
I've tried this in a simpler compose stack, while trying to retain most of the specifics you have in yours:
And it works fine:
Where do you see an error? Your first comment contains a warning. |
@realies let me investigate further when I have time, and will get back to you. Thank you., |
@realies can I rollback to a earlier version? |
You can check out this repository at an earlier commit and build an image from it. Probably better to debug what's going wrong if it does not work. Are you sure it does not work? |
Can someone help me understand why I am all of a sudden getting this error please?
s6-rc: info: service svc-openbox: starting s6-rc: info: service svc-novnc: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service svc-tigervnc successfully started s6-rc: info: service svc-openbox successfully started s6-rc: info: service svc-soulseek successfully started s6-rc: info: service svc-novnc successfully started s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-setup: starting Xvnc TigerVNC 1.13.1 - built 2024-04-01 08:26 Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101011 Tue Jun 11 19:26:01 2024 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started Warning: could not find self.pem Using local websockify at /usr/share/novnc/utils/websockify/run Starting webserver and WebSockets proxy on port 6080
The text was updated successfully, but these errors were encountered: