ubuntu18 container can't start anymore

[timothe]

Hi there,

The issue started 2 weeks ago, but I just flagged it. The image is updated automatically via watchtower and it seems the latest image for ubuntu18 can't start anymore. I'm using this version because it's running on Synology DSM 7.

Here's an extract of the container log:

[xvnc        ]  vncext:      VNC extension running!
[xvnc        ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc        ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc        ]  vncext:      created VNC server for screen 0
[supervisor  ] starting service 'nginx'...
[nginx       ] Listening for HTTP connections on port 5800.
[supervisor  ] starting service 'openbox'...
[openbox     ] ObRender-Message: Unable to load the theme 'OpenboxTheme'
[openbox     ] ObRender-Message: Falling back to the default theme 'Clearlooks'
[openbox     ] ObRender-Message: Unable to load the theme 'Clearlooks'
[openbox     ] Openbox-Message: Unable to load a theme.
[supervisor  ] service 'openbox' failed to be started: not ready after 5000 msec, giving up.
[supervisor  ] stopping service 'openbox'...
[supervisor  ] service 'openbox' exited (with status 1).
[supervisor  ] stopping service 'nginx'...
[supervisor  ] service 'nginx' exited (with status 0).
[supervisor  ] stopping service 'xvnc'...
[xvnc        ] Tue Jan  2 15:28:25 2024
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor  ] service 'xvnc' exited (with status 0).
[finish      ] executing container finish scripts...
[finish      ] all container finish scripts executed.

Not sure where the theme is coming from? Should I set it up again? Did anything change in the way it's setup? I can't find anything in the docs.

Thank you for your help.

[timothe]

Update: same issue when starting without initial config files, or with the latest ubuntu22 image

[timothe]

Update: I tried creating the container from scratch, checked permissions, still the same issue. The running user should have access to the theme, and the theme files are there, but it's not working anymore.

[traktuner]

Hello! It's probably a Synology permission issue. Would you please try to add the UID and GID environment variables to your docker run (or compose) command? USER_ID=0 GROUP_ID=0

and if that does not help, also add --privileged

We also added this to our troubleshooting tips (at the bottom): https://github.com/JonathanTreffler/backblaze-personal-wine-container?tab=readme-ov-file#troubleshooting

Please note that the new images will auto-update to a known-good Backblaze version when starting the container. Since the download could take some time you may see a black screen first, and then the installer opens.

Please let me know if that helps!

[traktuner]

As an additional info - I am also using a Synology NAS with this image, and since DSM 7.1/7.2 I was able to use the ubuntu20 and ubuntu22 images without a problem. Since we want to phase-out the ubuntu18 image, this would also be a great test! (ubuntu18 support was ended in april 2023)

[timothe]

@traktuner thanks for the kind reply. I used ubuntu18 because the latest was not working for me 😁 I'm afraid I already covered your recommendation previously and alas, with further tests, I get the same "unable to load theme" error.

GROUP_ID AND USER_ID are defined using a valid user and group (users group). For good measure I recreated the container with the latest image in Portainer, then from the DSM Container Manager. I also checked the permissions on the folders and files created in the config folder, via SSH. Alas, still the same issue. Screenshots enclosed.

Any idea? 😕

[traktuner]

Thanks for the screenshots! For me, on Synology, the only combination which works is "Execute container using high privilege" and UID+GID set to 0 (root). Does the container automatically stop when you start it? If it keep running, please post the full logs here (ssh into your synology, then sudo docker logs backblaze-new) Also there should be a separate log in [docker / backblaze config folder]/wine/drive_c/backblaze-wine-startapp.log Please also post this log if it's available. Then I can check if there's a specific problem with your setup. Thanks in advance!

[timothe]

There's progress! I changed the GID and UID to 0. The container WAS stopping, it is NOW running! 🎉 Now I have another issue... I have no visuals and it doesn't seem to run properly. It's running for 5 min and no change:

I got the logs from docker and wine: winelogs.log dockerlogs.log

[traktuner]

Hey! The backblaze-wine-startapp.log looks weird, I fixed an error last week that it actually shows the Backblaze version (in this log entry "Starting Backblaze version") so you are running an old image. Please delete the docker image and download it again (ideally the ubuntu20 or ubuntu22 tag). It should theoretically ask you 2 things if it's a clean install - "install wine mono" and after that the Backblaze installer should pop up. You may need to restart the container again. Let's see if there is some more progress ;)

[timothe]

Fresh install - good idea! I just did that, and it WORKS NOW!

You are my absolute saviour! Thanks so much for your work 🥇