Not sure if it's a feature request or a bug.
When trying to run minecraft-bedrock-connect, with a non-root user I end up with an error in the log.
Security best practices is to run the container as a non-root user to protect from hackers (very often 1000:1000, but can be really any uid/gid combo).
I get the following error in docker log:
2025-03-25T03:10:50.933379225Z time="2025-03-25T03:10:50Z" level=debug msg="Using /home/bedrock to match uid and gid"
2025-03-25T03:10:50.933407263Z time="2025-03-25T03:10:50Z" level=debug msg="Resolved UID=1000 from match path"
2025-03-25T03:10:50.933414642Z time="2025-03-25T03:10:50Z" level=debug msg="Resolved GID=1000 from match path"
2025-03-25T03:10:50.933503659Z time="2025-03-25T03:10:50Z" level=info msg="Skipping uid/gid change since current user is not root"
2025-03-25T03:10:50.936420089Z whitelist disabled
2025-03-25T03:10:50.936442144Z language disabled
2025-03-25T03:10:50.936446434Z custom_servers set to /config/custom_servers.json
2025-03-25T03:10:51.134107989Z Latest Bedrock Connect version is: 1.53
2025-03-25T03:10:51.134149848Z Downloading now Bedrock Connect JAR - version: 1.53
2025-03-25T03:10:51.136460357Z 2025/03/25 03:10:51 I! Retrieving https://github.com/Pugmatt/BedrockConnect/releases/download/1.53/BedrockConnect-setup.zip
2025-03-25T03:10:51.840924874Z 2025/03/25 03:10:51 E! unable to create destination file: open /docker/brc/BedrockConnect-1.0-SNAPSHOT.jar: permission denied
Not sure if it's a feature request or a bug.
When trying to run minecraft-bedrock-connect, with a non-root user I end up with an error in the log.
Security best practices is to run the container as a non-root user to protect from hackers (very often 1000:1000, but can be really any uid/gid combo).
I get the following error in docker log: