Repository navigation
Docker image v7.2.16 fails to start with permission error on virtuoso-entrypoint.sh #1377
Description
Activity
Development will have a look.
Reacted by sstamatiadis-dltHello again, I have tried again with versions
7.2.14,7.2.15,7.2.16. The problem starts from7.2.15.- I could not find anything related in the release notes and while comparing the entrypoint files it seems the main difference is the generation of the ssl certificate and keypair.
- I tried modifying my K8s pod seccomp profile without any success so far. I am running on K8s 1.33.
- I also ran the container locally and it managed to start without any issue (Docker host probably is a more permissive environment).
Reacted by Elias TzortzakakisDear virtuoso-opensource team,
Wondering if there is any update on this one? :-)
Initially we were unable to re-create this issue on our internal kubernetes instances on both linux and macOS.
The error message that your Kubernetes instance reported was a bit puzzling, as there had been no changes to the virtuoso-entrypoint.sh script, not the Dockerfile that would explain it.
Eventually we found out there is a problem with symlinks and docker image layers.
In 7.2.15 we started to squash the layers to get the absolute minimum size for our docker images.
What we did not know at the time, was that you then have to carefully order your RUN and COPY commands in order for the symlinks to be generated properly.
While this does not cause any problems for Docker, apparently this can cause problems for Kubernetes that does some extra checks.
We have just pushed the latest Virtuoso Open Source 7.2.17 to DockerHub
Let us know if this resolves the issue you reported.
Hello again, I have tried again with versions
7.2.14,7.2.15,7.2.16. The problem starts from7.2.15.- I could not find anything related in the release notes and while comparing the entrypoint files it seems the main difference is the generation of the ssl certificate and keypair.
- I tried modifying my K8s pod seccomp profile without any success so far. I am running on K8s 1.33.
- I also ran the container locally and it managed to start without any issue (Docker host probably is a more permissive environment).
I followed this comment, rolled back to
7.2.14and managed to deploy in openshift virtuoso as expected. i had tried withlatest -> 7.2.17which resolved incp: cannot stat '/opt/virtuoso-opensource/installer/virtuoso.ini.sample': Permission denied(even if i tried to runAsRoot)
Dear virtuoso-opensource team,
I am trying to deploy version 7.2.16. I noticed there is a hotfix release however on DockerHub I see only 7.2.16 which I am trying to deploy assuming it contains the hotfix.
I am deploying on Kubernetes and I get the following error which seems to be related with either incorrect permissions on the image part or some kind of pod restriction on my part.
Could you please provide some insights? The previous version 7.2.14 works without issues in the same K8s setup therefore I believe there might be a bug in the image build or some other breaking change which I missed in the release notes.