You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the debian image, the clamav user id and group id are both guaranteed to be 1000 whereas the alpine image specifies the user id as 100 and does not specify the group id. This leads to inconsistent behavior when switching between the different images. The alpine image should be ideally made to match the debian image so that permissions can be accurately set.
The text was updated successfully, but these errors were encountered:
The debian image has been altered some from the alpine image in order to support starting it as a non-root user. I believe this is why they differ in this case.
I don't think there would be any problem changing the alpine image to match, with uid and gid set to 1000. It's possible it would break some expectation for existing users. But ... probably would be okay.
There is a discrepancy between the UID and GID for the clamav user and group between the debian and alpine images:
https://github.com/Cisco-Talos/clamav-docker/blob/main/clamav/1.3/debian/Dockerfile#L123
https://github.com/Cisco-Talos/clamav-docker/blob/main/clamav/1.3/alpine/Dockerfile#L114
In the debian image, the clamav user id and group id are both guaranteed to be 1000 whereas the alpine image specifies the user id as 100 and does not specify the group id. This leads to inconsistent behavior when switching between the different images. The alpine image should be ideally made to match the debian image so that permissions can be accurately set.
The text was updated successfully, but these errors were encountered: