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

Support rewriting the image name #330

Open
natefoo opened this issue Jul 16, 2023 · 2 comments
Open

Support rewriting the image name #330

natefoo opened this issue Jul 16, 2023 · 2 comments

Comments

@natefoo
Copy link
Member

natefoo commented Jul 16, 2023

So that I can drop this hack

I am not sure, I think I tried an unstructured path rewrite for this and it didn't work, but I can check again, just didn't want to lose track of this issue.

@mvdbeek
Copy link
Member

mvdbeek commented Jul 20, 2023

Since the container resolution happens in Galaxy I think that would currently be the place where you would set this. I suppose a per destination container config would make sense. This is possible for the docker container resolver and would be relatively easy to set up. It would be nice though if pulsar could do the container resolution, container volume mounting and command line building, since then admins can set up a pulsar endpoint without having to adjust the Galaxy config for the specific settings of the pulsar destination.

@natefoo
Copy link
Member Author

natefoo commented Jul 21, 2023

I think maybe a proper integration of cvmfsexec might be nice as well, but maybe it's overkill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants