-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Valheim plus not installed #449
Comments
This is the important part of the log. In particular to; For whatever reason your docker container cannot access/download from Github. I suggest that you test your docker networking can in fact access the internet. I quickly added a generic alpine container to the same network I have my valheim server running on and;
Edit: Also just for the hell of it I used also curl as that is what is used via https://github.com/mbround18/valheim-docker/blob/main/src/scripts/start_valheim.sh#L87 ;
As you can see, the total file size is 10.2M, not the |
Hey, I am also getting this Issue.
I get the following error
However from the same running container if I wget the file to /tmp
Debug Logs look to indicate download is ok but what ever is parsing the zip isn't finding the manifest
Ran inspection of staging downloaded zip and it looks ok
Unfortunately, I don't know much about Rust but I would hazard a guess whatever is trying to get the manifest of the zip is failing valheim-docker/src/odin/mods/mod.rs Lines 105 to 111 in 4e8a2f2
|
It is an issue on your end, either Github or your routing. Fresh, new docker instance, full complete log;
Now the one section out of all of that;
Issue your end. Be it networking, ISP, etc. I run no http/s cache of any kind, nor behind any proxy. And I am even on shitty Australian NBN FTTN. |
I do not run behind and proxy's or caches that I am aware of (could always be weird ISP things) Went into the container and manually unzip the auto-downloaded /home/steam/staging/mods/UnixServer.zip built-in Linux commands are able to handle the zip fine The only thing I could think of is maybe a CDN issue missing some final bytes on the zip but the manifest looks like it should be something that's generated as it is not contained in the zip will try again in a few days once CDN / ISP caches have had a chance to clear out I did see there was a reupload by valheim plus so it could also be that (but that looks to only be affecting the .tar.gz not the zip) |
Just ran with an older container and it works fine no errors in v 1.4.3 I am only getting the manifest issues when using the latest image |
This is a dedicated server that is also running other docker containers without a problem. I tried downloading the files manually inside the container as user steam and root without a problem.
|
Oh for fucks sake....... You are both correct. DockerHub is prob caching my ISP. It wasn't until I compared the digest of the image from Dockerhub to what I was downloading and took a closer look at both of your logs. I humbly apologize to you both. This is indeed reproducible. Somewhere between f9c64a9 & 0526859 is the cause (odin 1.4.1 -> 1.4.2). I don't know enough about Rust to state what it is. The only commit that happened between those two Odin versions that has the text |
Each test I flushed the mount data to ensure clean downloads each time. This is with |
@spannerman79 checking on this now |
On a fresh instance created with I have not tested other mods added in with Log of new docker instance.
|
Hello,
I have enabled Valheim+ in the docker-compose file but I get an error when it tries to get the file while starting up.
The text was updated successfully, but these errors were encountered: