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
Why is this not part of the image build process? Why is done at runtime (which requires write permissions to /var/www/ which causes problems on e.g. OpenShift?
Or, if I understand this line from the Dockerfile properly, why is this done again in the entrypoint?
Seems like this was done to allow opencost-ui to run in a read only file system
How is adding a cp command to the entrypoint supposed to help with running on a read-only filesystem? Unless /var/www is being mounted from a volume and is writable?
Dear maintainers,
while trying to get OpenCost running on OpenShift, I had a look at the UI image.
Once thing I noticed is this line:
opencost-ui/docker-entrypoint.sh
Line 4 in 459ddc5
Why is this not part of the image build process? Why is done at runtime (which requires write permissions to
/var/www/
which causes problems on e.g. OpenShift?Or, if I understand this line from the
Dockerfile
properly, why is this done again in the entrypoint?https://github.com/opencost/opencost-ui/blob/main/Dockerfile#L30
Kind Regards,
Johannes
The text was updated successfully, but these errors were encountered: