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
@njriasan can you clarify this a bit more? do you mean docker containers spawned by kubernetes? kubernetes is container management software, not containerization technology, so it won't manage volumes directly, will it?
My understanding is that you can specify volume creations in the description for pod. It also lets you specify container permissions by associating each docker container with a security group. My understanding is that in addition to adding the volume though you also need to go through a step to ensure your container can properly access the volumes. What I read suggests that containers have user permissions and volumes mount with root:root. There may also be a permissions issue with enabling mount on this volume.
My understanding, based on this stack overflow post, is this requires 3 changes: make the dockefile creates a new usergroup for the container, add the mounted volume, and modify it to add permissions to that user group so mount succeeds.
I may also need to modify the Kubernetes implementation to use deployment files in addition to service and pod files, but I haven't fully investigated that.
Kubernetes default doesn't have a volume mounted and the database container may not have the necessary permissions to use it.
The text was updated successfully, but these errors were encountered: