[GH-ISSUE #109] Feedback on Container User Permission Change in versions newer than netbootxyz/netbootxyz:0.7.5-nbxyz9 #30

Closed
opened 2026-02-27 14:47:30 +03:00 by kerem · 1 comment
Owner

Originally created by @notylou on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/109

Hello,
I've noticed an apparent change in the container's internal user permissions for Docker image versions newer than netbootxyz/netbootxyz:0.7.5-nbxyz9.
Specifically, after updating to a newer version, the container fails to start or run correctly if I continue to use the PUID and PGID environment variables in my Docker CLI command or Docker Compose configuration to specify the user and group. The container only runs as expected after I remove the PUID and PGID settings from my configuration.
I have reviewed the project's README and release notes, but I could not find any explicit documentation regarding this permission change. This might cause confusion for users who are upgrading from an older version.
Could you please clarify if this is an intentional change? If so, would it be possible to add a note about this in the documentation? If this is an unintentional bug, I hope the development team can look into it.
Thank you

Originally created by @notylou on GitHub (Sep 18, 2025). Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/109 Hello, I've noticed an apparent change in the container's internal user permissions for Docker image versions newer than netbootxyz/netbootxyz:0.7.5-nbxyz9. Specifically, after updating to a newer version, the container fails to start or run correctly if I continue to use the PUID and PGID environment variables in my Docker CLI command or Docker Compose configuration to specify the user and group. The container only runs as expected after I remove the PUID and PGID settings from my configuration. I have reviewed the project's README and release notes, but I could not find any explicit documentation regarding this permission change. This might cause confusion for users who are upgrading from an older version. Could you please clarify if this is an intentional change? If so, would it be possible to add a note about this in the documentation? If this is an unintentional bug, I hope the development team can look into it. Thank you
kerem closed this issue 2026-02-27 14:47:30 +03:00
Author
Owner

@tenfourty commented on GitHub (Sep 22, 2025):

I think the issue comes from this commit: github.com/netbootxyz/docker-netbootxyz@ca7a3390c2

<!-- gh-comment-id:3318768660 --> @tenfourty commented on GitHub (Sep 22, 2025): I think the issue comes from this commit: https://github.com/netbootxyz/docker-netbootxyz/commit/ca7a3390c28ee6e5d57ef904b018ee2c7fb9cad4
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-netbootxyz#30
No description provided.