Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Images: don't put pelican binaries into /pelican #1744

Open
matyasselmeci opened this issue Nov 15, 2024 · 0 comments
Open

Images: don't put pelican binaries into /pelican #1744

matyasselmeci opened this issue Nov 15, 2024 · 0 comments
Assignees
Labels
container enhancement New feature or request
Milestone

Comments

@matyasselmeci
Copy link
Contributor

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.

@matyasselmeci matyasselmeci added enhancement New feature or request container labels Nov 15, 2024
@matyasselmeci matyasselmeci added this to the v7.12.0 milestone Nov 15, 2024
@matyasselmeci matyasselmeci self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
container enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant