Closed kernohad closed 7 months ago
Hey @kernohad could you please do a clean new fresh install with the latest image forcefully pulled and a fresh docker-compose?
I tried it all again with a fresh copy of your image from the hub, and the backup is working.
So it appears to be an issue with me building the image myself. Any pointers?
I tried it all again with a fresh copy of your image from the hub, and the backup is working.
Glad to hear that 😄
So it appears to be an issue with me building the image myself. Any pointers?
Im not sure what you mean by that, English is not my native language, could you please elaborate on* this? I dont understand.
At first I copied the Dockerfile you have in the repo and was running docker build --tag 'palworld-dedicated-server
myself to generate the image. Then I was using that image to run the container instead of pulling the image you published to docker hub.
It appears when I build the image locally, it fails to backup. I made sure to copy the latest Dockerfile you had with the Supercronic and chmod=777 for the backupmanager.sh ; still seemed to give me issues.
It is working now using the image from docker hub, but I am more just curious now if I can get it working by building the image locally.
At first I copied the Dockerfile you have in the repo and was running
docker build --tag 'palworld-dedicated-server
myself to generate the image. Then I was using that image to run the container instead of pulling the image you published to docker hub.It appears when I build the image locally, it fails to backup. I made sure to copy the latest Dockerfile you had with the Supercronic and chmod=777 for the backupmanager.sh ; still seemed to give me issues.
It is working now using the image from docker hub, but I am more just curious now if I can get it working by building the image locally.
I have the same issue when building myself. It seems to be some kind of permissions issue. I haven't looked into it too closely. OS: Tried on both Arch and Ubuntu
I ran into this issue, running chown -R 1000:1000
(or whatever PUID/PGID you're using) and/or chmod -R 755
the directory fixed it for me.
I ran into this issue, running
chown -R 1000:1000
(or whatever PUID/PGID you're using) and/orchmod -R 755
the directory fixed it for me.
I have these two lines in the Dockerfile, like the one from the repo. Is this what you mean or something else?
ADD --chmod=777 servermanager.sh /servermanager.sh
ADD --chmod=777 backupmanager.sh /backupmanager.sh
A work around is to add the following after the volume creation (VOLUME [ "/palworld" ]
):
Note that I haven't tested if having steam own /palworld will cause any issues.
...
USER root
# Create the directory and change permissions
RUN mkdir -p /palworld && \
chown -R steam:steam /palworld && \
chmod -R 775 /palworld
USER steam
...
A work around is to add the following after the volume creation (
VOLUME [ "/palworld" ]
):Note that I haven't tested if having steam own /palworld will cause any issues.
... USER root # Create the directory and change permissions RUN mkdir -p /palworld && \ chown -R steam:steam /palworld && \ chmod -R 775 /palworld USER steam ...
Ah gotcha. I am curious as to how @jammsen got the image to work fine with the docker file in the repo; without doing this workaround that is.
Oh I just realized there is a pull request for this #45.
Ah gotcha. I am curious as to how @jammsen got the image to work fine with the docker file in the repo; without doing this workaround that is.
I'm wondering the same.
It is working now using the image from docker hub, but I am more just curious now if I can get it working by building the image locally.
@kernohad - Please go ahead and use my image on docker-hub that way you get always the latest stuff the easy way.
Why its not working for you im not sure, because i dont know your setup. Mine is very simple, W11 Pro, WSL2 default install, Image Ubuntu, Docker-Deskop latest version and my User-ID in WSL2 is 1000.
Its really bare-minimal (almost wrote bare-metal 🤣), because i want it to be similar then a fresh ubuntu/debian install with just 1 user and UID/GID 1000 for it. Thats like the 90% percentile solution for most people i know.
A work around is to add the following after the volume creation (
VOLUME [ "/palworld" ]
):Note that I haven't tested if having steam own /palworld will cause any issues.
... USER root # Create the directory and change permissions RUN mkdir -p /palworld && \ chown -R steam:steam /palworld && \ chmod -R 775 /palworld USER steam ...
This is acutally what docker install does with this me switching to USER steam and den defining the volume ... Its weird, that you guys need that. What Docker-Version do you guys have?! Im running on 3-5 days old 25.0.0 (docker-node) and 24.0.7 (WSL2-Docker-Desktop) and everything is working perfectly.
Ah gotcha. I am curious as to how @jammsen got the image to work fine with the docker file in the repo; without doing this workaround that is.
I'm wondering the same.
ME AS WELL, can we make a Discord CALL please?
I wouldn't worry about it as PR #45 solves this issue and it also solves the duplicate issue #52. It's similar to what I did in that code snippet except cleaner.
I customized #45 a bit but added it earlier today.
Im closing this issue as resolved, feel free to try it out and reopen again if needed.
If you like this project, please consider giving this repo and the docker-hub-repo a Star.
Have you read the Important information text above
Current behavior
When the backupmanager cron job kicks off, it fails to find /backupmanager.sh![image](https://github.com/jammsen/docker-palworld-dedicated-server/assets/17996635/456827a5-8e93-4c52-9ed4-2062569bbaef)
Desired behavior
backupmanager script can be found and backs up as expected.
Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:
Software setup
Hardware setup
Additional context
I have attempted to build the image myself as well as use your image.