sco-atolcd opened a new issue, #6031:
URL: https://github.com/apache/hop/issues/6031
### What would you like to happen?
### Feature Request / Improvement
Currently, the `web` Dockerfile explicitly sets a fixed UID/GID for the
`hop` user, which makes volume permission handling predictable and allows users
to `chown` mounted volumes anonymously on the host without creating a matching
system user.
The standard/main image, however, relies on the default auto-assigned
UID/GID created by `adduser`. This forces anyone using bind-mounted volumes to
create a local user named `hop` with the exact same numeric UID/GID on the host
system — otherwise file permissions are mismatched and processes inside the
container can't write to the volume.
### Proposed solution
Add an explicit, fixed UID/GID for the `hop` user in the main/standard
Dockerfile, ideally matching the one used in the `web` for consistency (501).
Example:
```dockerfile
ARG HOP_UID=501
ARG HOP_GID=501
RUN addgroup -g ${HOP_GID} -S hop \
&& adduser -u ${HOP_UID} -S -D -G hop hop
### Issue Priority
Priority: 3
### Issue Component
Component: Containers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
