Skip to content

Conversation

@videlanicolas
Copy link

masterserver.sh writes the new server creds to this folder. This is being called as user pwn3 inside the container and there is no check that the user pwn3 has write access to this file. This makes sure that the permission is granted.

masterserver.sh writes the new server creds to this folder. This is being called as user pwn3 inside the container and there is no check that the user pwn3 has write access to this file. This makes sure that the permission is granted.
@mattypiper
Copy link

This issue occurs for me as well, and I believe approving the pull request will fix it.

For me, I fixed my container with:

docker exec -it $CONTAINER bash
chown -R pwn3:pwn3 /opt/pwn3

I added a sleep 60 to the end of gameserver.sh to keep the container alive after the SIGSEGV so that I could fix the permissions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants