Won't install client

[Pl4ytimes666]

After i install all Wine Components the client said that he has no network connection.
What am i doing wrong ?

[JonathanTreffler]

Can you check whether the docker has access to the internet by going into the console and pinging google.com for example?

[JonathanTreffler]

Were you able to fix the issue?

[traktuner]

Same happens with my client.
https://ca000.backblaze.com can be accessed (wget) with no issues from within the container.

[JonathanTreffler]

Do you do anything fancy network-wise? Container network routed through a VPN? Syste wide network proxy? Router with special Firewall Rules?
And which OS are you using ? Unraid ?

[JonathanTreffler]

Have you tried removing the container and all the mounted configuration folders and starting the installer again?

[traktuner]

Hi,
I am using a Synology NAS as the docker host. No VPN. I also tried the container from @Atemu which does not display this error and goes straight to the login screen. So I assume it has something to do with the ubuntu base image.
Removing the contents of the config folder and starting the installer again -> same issue. It installs mono and then displays the "could not communicate" error.

[traktuner]

Update:
It's working for me now. I built the Docker image by myself and used the older 18.04 baseimage. So there has to be a small dependency which is leading to this error. Also debian-10 is working, debian-11 -> same error.
Changes in my forked repo: https://github.com/traktuner/backblaze-personal-wine-container

[JonathanTreffler]

Ok, if we cannot figure out what is causing the issue with the newer base image i could merge your fork into a second branch, publish it under a second tag and add an entry to the troubleshooting section in the readme.
Thanks for your debugging :)

[traktuner]

You're welcome! Feel free to merge, would be cool if it also helps @Pl4ytimes666 to get it working :)

[cliss]

I'm having the exact same problem as @Pl4ytimes666. I'm also hosting on a [very old] Synology NAS.

I attempted to run/build @traktuner's Dockerfile by hand, but I couldn't get it to work properly. (This is surely user error.)

Would love to see these fixes merged, if at all possible, please, @JonathanTreffler!

[JonathanTreffler]

Ok, i will merge it today or tommorow and release It under a separate tag :)

[cliss]

Thanks so much, @JonathanTreffler 🥰

[JonathanTreffler]

Sorry it took a few more days, i will merge and publish it now :)

[JonathanTreffler]

The ubuntu18 tag is currently being built by the Github Action.
@cliss Would be great if you could test if it fixes your problems once it is done :)

[cliss]

Still didn't work for me, but I wonder if this is user error.

Unless I'm unaware, this container isn't published in any sort of registry, right? So I'm trying to roll this all by hand, which is new to me. Regardless, when I run, I get the following.

I haven't seen this before.

s6-applyuidgid: fatal: unable to exec /startapp.sh: Exec format error
[services.d] stopping services
[services.d] stopping app...
[services.d] stopping statusmonitor...
[services.d] stopping certsmonitor...
[services.d] stopping nginx...
[services.d] stopping logmonitor...
[services.d] stopping openbox...
[services.d] stopping x11vnc...
caught signal: 15
21/03/2022 13:19:40 deleted 40 tile_row polling images.
[services.d] stopping xvfb...
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.