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
OpenProject 13.3.0 running helm chart 4.5.0, upgrading from 13.0.7 and unknown helm chart version prior.
We have a bare metal kubernetes cluster and it seems #38 changed the way tmp and its new volumes are mounted. It looks like there is a "sort of" workaround where develop: true changes the way those volumes are mounted, and it does seem to work, albeit we have errors about HTTPS since that also is bundled together.
The logging error is below, while attempting to upload a logo in the admin/design page.
# /usr/local/lib/ruby/3.2.0/tmpdir.rb:34:in `block in tmpdir': system temporary path is world-writable: /tmp (StructuredWarnings::StandardWarning)
# /usr/local/lib/ruby/3.2.0/tmpdir.rb:34:in `block in tmpdir': /tmp is world-writable: /tmp (StructuredWarnings::StandardWarning)
# 2024-02-16 18:18:26 +0000 Rack app ("POST /admin/design" - (ipaddress)): #<Errno::EROFS: Read-only file system @ rb_sysopen - /app/RackMultipart20240216-12-lup1dp.svg>
A further note, it's misleading to have tmp volumes while persistence.enabled: false. I went back to read the values comments and it does say "data directory" but I did not immediately make any connections here.
A secondary note, we have s3 turned on with direct upload, why does this even need to go to a tmp dir? Maybe the real fix here is to convert the rest of the custom design stuff to also use direct upload.
Thanks!
The text was updated successfully, but these errors were encountered:
Another workaround is setting useTmpVolumes and containerSecurityContext.readOnlyRootFilesystem to false,
what is also not optimal, but this will leave the use of https enabled.
OpenProject 13.3.0 running helm chart 4.5.0, upgrading from 13.0.7 and unknown helm chart version prior.
We have a bare metal kubernetes cluster and it seems #38 changed the way
tmp
and its new volumes are mounted. It looks like there is a "sort of" workaround wheredevelop: true
changes the way those volumes are mounted, and it does seem to work, albeit we have errors about HTTPS since that also is bundled together.The logging error is below, while attempting to upload a logo in the admin/design page.
A further note, it's misleading to have
tmp
volumes whilepersistence.enabled: false
. I went back to read the values comments and it does say "data directory" but I did not immediately make any connections here.A secondary note, we have s3 turned on with direct upload, why does this even need to go to a tmp dir? Maybe the real fix here is to convert the rest of the custom design stuff to also use direct upload.
Thanks!
The text was updated successfully, but these errors were encountered: