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
currently, the Grobid service requires root privileges to be running in a Kubernetes environment. However, running a container as root in a production environment is not recommended. Are there any plans to have Grobid service running as rootless container or nonroot privileged container (with a specific id)?
E.g.,: The container fails in the intialisation process when run as nonroot due to issues creating tmp directory and read-only file system:
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue @vipulg13. I'm not sure how long may take, it could be to re-engineer the whole build.
We can find a solution on that for version 0.8.2 as we are freezing changes for version 0.8.1.
Dear team,
currently, the Grobid service requires root privileges to be running in a Kubernetes environment. However, running a container as root in a production environment is not recommended. Are there any plans to have Grobid service running as rootless container or nonroot privileged container (with a specific id)?
E.g.,: The container fails in the intialisation process when run as nonroot due to issues creating tmp directory and read-only file system:
The text was updated successfully, but these errors were encountered: