-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Start up file permission denied #2510
Comments
I'm guessing it's because that file gets written as root user during initial container startup. I'll have it remove pre-existing file as root, but write it just a little bit later as regular user (uid=1000). |
When this build finishes, please see if pulling that image resolves your issue. If it doesn't, you can re-open this and provide any new errors/issues it reports. |
Getting the same error, new line number:
Don't see a way to re-open the issue. If I delete the .rcon-cli.env file the server gets a bit further, I see the file is recreated as well. This is a different server from the compose I posted earlier. And forge is installed but re-installs it because I am assuming it can't read the file. The file /data/.forge-manifest.json already exists and was created by the first run of the server.
|
I'll re-open for discussion sake, but there's some various file ownership mismatches going on with your setup. Since you're using CIFS, then that'll beyond the typical things I can offer to debug. |
After further testing in the container, I determined it was something specific to dotfiles when I was in the container: Could create a new dotfile but would not allow overwriting.
Standard (non-dotfile) files I could create and overwrite:
Fixed this by updating my smb share to hide dot files = no and things appear to be working. Haven't had a chance to look deep into this and may be unrelated since I recreated the share as part of this. |
Describe the problem
I have a few minecraft servers running in Docker for a while but recently ran into a startup issue. This is the error I receive:
I recently updated the the docker server packages and restarted the server when I think the issues begin. Not sure if it pulled a newer image as part of that or not.
A new server with this same docker compose will start fine using an empty directly and can write files but if I restart the new server it fails with the above error. Appears it can not modify the existing file for some reason at start up. I assume it is something to do with using a volume mount but it had been working until recently. Any direction would be helpful as I have tried multiple changes to the file share and the container security/user values.
Also I moved a new minecraft server to Kubernetes and see the same issue, a new instance of minecraft starts correctly but if I delete the pod it will have the same error when creating the new pod using the existing files on the fileshare. This is using the same file share. So think it is either the file share or container having an issue but can't put my finger on what is going on.
Container definition
Container logs
The text was updated successfully, but these errors were encountered: