-
Notifications
You must be signed in to change notification settings - Fork 157
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
Unable to start container process: exec: "/servermanager.sh": permission denied - Day 1 Release Bug-Fixes - Community-Thread #1
Comments
Yep so I'm not the only one. Trying to compare this project to other SteamCMD based dedicated servers to find the issue until the maintainer takes a look... |
I'm having this problem too. |
I have the same issue, I think the probleme can be solve by add |
Im on it and testing fixes right now. |
Thanks bro. I had 20 tabs open trying to figure it out myself. Hope it works! |
That bug is fixed, now it seems like Volumes wont be recognized |
Awesome. The container deployed this time. Now I will test to see if it works properly. I appreciate your quick response to this issue! |
AH got the error identified ... really weird though Guys make sure you do |
Can you be more detailed? I'm not that familiar with Linux systems,thks |
On your Docker-Host you created the docker-compose.yml and the |
Can I see your compose file? |
For mine it's
Which means /config/palworld is my bind mount for the container's /palworld directory So I have to run |
I think we are all in the same boat right now. Also can't see in Community Browser or direct connect. |
same for me, looks like sth. error |
If that's true than steamcmd needs to be configured to authenticate via a steam account instead of anonymously. I hope this isn't the case. |
for me the server is working since I entered the command chmod 777 game. But only the direct connect works, I dont find the server in the server browser. I also entered a server password in the yaml file but I am able to connect to the server without a password. |
Per their documentation, that's intended (https://tech.palworldgame.com/dedicated-server-guide#qa):
|
Im getting this S_API Fails too, seems to be normal i've tried the image for Unraid from an buddy called @ich777 and his does the same thing. The forum-post of him is helpful ( https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/page/365/#comment-1355891 ) - There it says you cant use password for direct-connect, if you want that you need to "wait" until the master-server lists you, sometimes this can take longer then 5 minutes, other people also says they had to click multiple times "next 200 results" to get an update. So no-password and direct-connect (its a known bug) or wait longer to be in the Community-List and you can use a password then. |
Random but I wasn't able to connect to my dedicated server because Docker was assigning 8211 TCP instead of UDP. Changing to UDP fixed it.... Finally I'm connected to something! |
My UPD 8211 port is already open, but the IP still cannot access it |
looks like my server is in the community list now, but still doesn't require a password when trying to connect even with the flag set to |
|
Also unable to connect still |
Pushing latest fixes now |
Everything is pushed, please go ahead and test it and give me feedback. I cannot say enough how important it is to start FRESH, pull image fresh, make a new docker-compose.yml from the template and delete |
Works for me now as well, only thing that I noticed was |
steamclient-so and the S_API Warnings/Error seem to be normal, almost every other game based on that offically recommended SteamCMD-Base-Image seem to have the same problems. |
|
Huh wait? Adding chmod or anything should not be needed, most likely you builded the image but forgot to apply default permissions on the servermanager.sh Did you do chmod +x servermanager.sh before building the image? |
Huh, what do you mean? |
Also please if like my work, please consider to give me a Star on Docker Hub and here an Github please, that would mean so much to me |
I renamed this isse to "Unable to start container process: exec: "/servermanager.sh": permission denied - Day 1 Release Bug-Fixes - Community-Thread " - Hope thats okay with okay @Fifthdread . I will closed this, as so many bugs yesterday were found and solved. Feel free to create a new issue if you find something else you need help with. Thanks a lot for your input, hardwork and dedication! |
Came here to say that the root complaint here still seems unfixed on a fresh install (I arrived here today, hi!) |
如果你在 chown 以后仍然 permission denied |
Hello When I try to build with the dockerfile I have this error
When I change in the Dokerfile To I have |
Hey @kaysan13 if you need help create a new issue, DONT necro old posts, none of the previous people here have agreed to that! |
Have you read the Important information text above
Current behavior
Container will not start with the provided Docker Compose. Trying to deploy the container via Portainer. I created an app-template using the provided Docker Compose and I receive the below error when trying to deploy the image:
Deployment error
failed to deploy a stack: Container palworld-dedicated-server Creating Container palworld-dedicated-server Created Container palworld-dedicated-server Starting Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/servermanager.sh": permission denied: unknown
This could be a lack of understanding on my part. Thanks for any help you can provide.
Desired behavior
Container should start
Links to screenshots
To Reproduce
Steps to reproduce the behavior:
Software setup
Hardware setup
Additional context
No response
The text was updated successfully, but these errors were encountered: