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
We had one site bind-mount their storage dir over /pelican, which caused an error at startup because the binaries were no longer there.
We do not prescribe a location for where data should be mounted, and IMO /pelican is a perfectly reasonable choice; we should avoid the issue by moving the binaries to some different location.
It is good practice to follow the Filesystem Hierarchy Standard, even in containers. The pelican and osdf binaries should be moved into /usr/local/bin.
The text was updated successfully, but these errors were encountered:
We had one site bind-mount their storage dir over
/pelican
, which caused an error at startup because the binaries were no longer there.We do not prescribe a location for where data should be mounted, and IMO
/pelican
is a perfectly reasonable choice; we should avoid the issue by moving the binaries to some different location.It is good practice to follow the Filesystem Hierarchy Standard, even in containers. The
pelican
andosdf
binaries should be moved into/usr/local/bin
.The text was updated successfully, but these errors were encountered: