-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Latest update require wine to run the docker image #80
Comments
Oh, one more question, how to specify the image VERSION in the zwift.sh file? Obviously, latest works, but say an image that is a few days old? |
You can try setting the VERSION=1.60.0 zwift.sh I think the updater scripts would override previous image tags. |
Thanks, found it... |
|
Hmm... That is strange. I did stop all the containers, and deleted all of the images, re-downloaded the latest one, still the same behavior. |
if I click install, at the Wine Mono Installer, I get the following screen later: Wine Mono seems to be already included in the docker image: Line 82 in 24ac826
I noticed that afterwards there is a Zwift icon in my tray. If i right click it and click on open, I get an error message, telling me that WebView2 needs to be installed. For the moment I'm also using a workaround, I changed line 8 in the /usr/local/bin/zwift file to 1.61.0 did not work for me. |
Has anyone tried building the latest locally using |
just tried, but fails for me. However, this could be something completely unrelated since I have never build it in the past...
|
I tried to build locally as well, and if I recall correctly, I also got this error message. Will check once I get home just to make sure. |
Tried building from scratch locally and seems to build ok but that is probably because i have an old cache. if i try to build it with github actions i get
However, even tho im building it correctly, when i run i get So not sure what is going on, and I don't have time right now to look into it any further, so i guess you should simply use |
Just to confirm what is already known. Building the image locally fails for me as does for @jdohm . EDIT: On a closer look, this looks to be the original issue.
|
It's most likely related to the image installing from Debian unstable It would probably be best to base the image on a rolling release distro or to use the Debian unstable image. |
Can anyone try to build #81? |
Yes, just tried it. The image seem to build, but it still doesn't seem to work. |
@nowave7 i fear you are running the wrong IMAGE after build_image.sh try running |
@netbrain EDIT2: Still the same in the end. Mono installation missing. |
You need to click Install when it prompts for Wine mono. |
@quietvoid |
I don't know. You could always rename the image tag in the |
I took your advice @quietvoid and renamed the image version tag, and it seem to have worked now. Thanks! |
Yes 1.61.0 is still the latest (1.62.0 is out but not for everyone yet). |
Good to know, but as @quietvoid pointed out, going back to bookworm might cause issues with graphics drivers for other users. so im trying to upgrade to sid across the board, but seems to be a couple of snags in order to get that working. Might look into using something else than debian as the base image. getting it to work with alpine with xorg and wayland would probably be the best. |
Actually got zwift to work on alpine now pretty easily in my POC, so think i might swap out debian for alpine as a test to see if this would fare better over time.. 🤞 , this was also running wine 9.0 which has native experimental support for wayland |
let us know if you need additional testers :) |
Got it working using the image tag. Available for testing too if needed! Thank you for this! |
Weird thing is, i got it working pretty easily on my POC when just hacking away and running everything manually, now when trying to run everything through the automated docker environment. things seems to fail in unexplainable ways 😞 . In any case if people wan't to tag along and maybe learn a thing or two, here is a way you can try to install zwift on your own in an ephemeral environment:
Your docker command may vary depending on hardware, if nvidia, would probably suffice with --gpus all for graphics My example is running alpine:edge image, but you can experiment with others if you like, Now that you have a running alpine environment running, first experiment should be to see if graphics is working and can be forwarded to host. so add mesa-utils and mesa-drivers.
you should now see some spinning gears, if not your graphics device is probably not available in the container or you are missing some drivers. If things are still working you should now be ready to install wine and zwift.
You can test that wine is working by issuing the command next you also need/want winetricks and some other utilities
Replace WINETRICKS_VERSION with a suitable version. next to install zwift you require dotnet48, install by issuing then finally download zwift If all goes well you and everything installs you should then be ready to launch zwift, however this is where some runfromprocess-rs is required. Please refer to the entrypoint.sh on how runfromprocess-rs.exe is run in conjunction with ZwiftLauncher.exe. But in essence runfromprocess is used to simulate that ZwiftApp.exe is being run or forked off a parent process ZwiftLauncher.exe. In order to get a hold of this runfromprocess-rs application you can either compile the source code yourself, or copy it from an existing docker container, the latter probably being the easiest. Something along the lines of :
You should now have your own copy of runfromprocess-rs in the alpine container which you can use to launch zwift. Also take a look at my zwift.verb file which you can use to install zwift on a more automated way.
Ill hopefully soon get around to create a fully automated system, and in any case would be great if you guys would manage to create a reproducible build of zwift using alpine or any other tiny image for that matter. Let me know how you fare, I've butted against quite a few issues, probably more than described in this post. |
Just got it working again now manually, seems to be some issue creeping up when running things in unattended mode. Not sure why. but i'll look into it more in the next few days, hopefully. 🤞 |
I've also now rolled back to 1.60.0 being the latest in docker hub and paused zwift update github action as to not create new failing container images. |
I've mentioned it before but I maintain my own image based on Arch Linux here:
I haven't tried making it compatible with NVIDIA GPUs, so it's only missing that. The Wayland only version is semi-broken since the Wine Wayland driver is very new. |
shameless self-promotion 🤣 Yeah, archlinux is definitely an option. But i would prefer if we could use alpine or something more lightweight. Not saying that archlinux is wrong in any way, im a fan. But ideally i'd like to have a statically compiled wine binary on a scratch docker container and nothing else. But that's not going to happen in any time soon. So the closest were gonna get right now is something like alpine. |
I guess it's time for me to get intimate with docker... :D |
the latest changes to #81 now works, please give it a go. I have not optimized this, for instance installing webview2 from external url might be unnecessary as zwift seems to provide it's own webview2. But atleast now we have a starting point for optimizing it further. |
using alpine seems to give a good image size reduction on unpacked images
Will be exciting to see the gzipped down size of the image when uploaded to docker hub 🤗 |
Building locally as we speak... |
I can confirm that x11/xorg with intel works fine with xwayland, however pure wayland does not (setting DISPLAY=""). Seems to fail on detecting graphics driver. however sound/pulseaudio works. So should be feature wise identical to the debian alternative. |
It's just downloading Zwift files in the background. Give it some time, it should finish. You can verify this by tailing the Zwift launcher log file. |
Oh, okay, I have gotten a little impatient. Will give it another go :) |
Try running the above while updating. |
@netbrain is there any way to message you directly? I've clicked around here on github but can't find anything. Just wanted to say thank you! Also, did my first zwift tonight with the docker running on Ubuntu at a very nice 4k resolution on the TV in my garage. Fantastic! |
No sorry, not very active on any social media or Im platforms. However, comments like these that make it all worthwhile, thanks🤗👍 |
works fine for me on KDE Plasma using x (building and running it)
on wayland (also Plasma) im not able to start, however that could be me just not knowing how to use docker :) (on x i just started the zwift container, i created before, with |
Describe the bug
The update to the image done on 01.04.2024 suddenly requires wine/wine-mono to be installed on the machine.
To Reproduce
Steps to reproduce the behavior:
run zwift as normal
Expected behavior
Zwift image should start and it should run normally
Screenshots
Additional context
System details, even though it ran just a few days ago, and no changes were done to the host system:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
Linux xxxx-OptiPlex-9020 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Selecting the install doesn't seem to have any effect.
The text was updated successfully, but these errors were encountered: