-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Docker image uses VOLUME directive incorrectly #364
Comments
Furthermore, the turning of
About 360 MB per volume in case of Pro version, or 280 MB in Community version:
|
jakubgs
added a commit
to status-im/infra-role-openkm
that referenced
this issue
Dec 4, 2023
Since the original image misuses `VOLUME` directive and makes it impossible t actually change permissions for `/opt/tomcat`: openkm/document-management-system#364 https://support.openkm.com/tickets.php?id=13006 Signed-off-by: Jakub Sokołowski <[email protected]>
jakubgs
added a commit
to status-im/infra-role-openkm
that referenced
this issue
Dec 4, 2023
Since the original image misuses `VOLUME` directive and makes it impossible t actually change permissions for `/opt/tomcat`: openkm/document-management-system#364 https://support.openkm.com/tickets.php?id=13006 Signed-off-by: Jakub Sokołowski <[email protected]>
jakubgs
added a commit
to status-im/infra-role-openkm
that referenced
this issue
Dec 4, 2023
Since the original image misuses `VOLUME` directive and makes it impossible t actually change permissions for `/opt/tomcat`: openkm/document-management-system#364 https://support.openkm.com/tickets.php?id=13006 Signed-off-by: Jakub Sokołowski <[email protected]>
jakubgs
added a commit
to status-im/infra-role-openkm
that referenced
this issue
Dec 4, 2023
Since the original image misuses `VOLUME` directive and makes it impossible t actually change permissions for `/opt/tomcat`: openkm/document-management-system#364 https://support.openkm.com/tickets.php?id=13006 Signed-off-by: Jakub Sokołowski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the official Docker image applies the
VOLUME
directive to the/opt/tomcat
folder:But this is wrong if you look at the documentation for Docker:
Since
/opt/tomcat
folder contains software in form or JARs, WARs, and scripts, it is not supposed to be a volume, since volumes are intended for "data generated and used Docker containers". This meansVOLUME
directive was used incorrectly.Furthermore:
This in effect means that it is impossible to modify the
/opt/tomcat
folder - for example to change permissions - since it's a volume:Such a
Dockerfile
intended to allow the container as non-root user will have no effect, since the/opt/tomcat
folder is a volume.The correct usage of
VOLUME
directive would be for folders like/opt/tomcat/conf
or/opt/tomcat/data
, not/opt/tomcat
.The text was updated successfully, but these errors were encountered: