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

Feature request: support for --insecure during apptainer push and pull #2054

Open
anderbubble opened this issue Feb 29, 2024 · 1 comment
Open

Comments

@anderbubble
Copy link
Contributor

apptainer pull uses HTTPS by default. HTTPS can be disabled with --no-https; but in circumstances where HTTPS is desired but a self-signed certificate is in use, we would like to be able to use --tls-verify=false or similar.

If this is already possible with an environment variable, that would be fine; but I haven't been able to find such an option.

@DrDaveD
Copy link
Contributor

DrDaveD commented Mar 4, 2024

I suggest an --insecure option to be like curl. It would need to be on pull, build, action commands run/start/exec, and instance start/run. There is already an option by that name on remote add although the description says it applies to only http, not https. I would think that should be extended to https if it isn't already, or the description changed if it already includes https.

@anderbubble anderbubble changed the title Feature request: support for --tls-verify=false during apptainer pull Feature request: support for --tls-verify=false during apptainer push and pull Mar 19, 2024
@anderbubble anderbubble changed the title Feature request: support for --tls-verify=false during apptainer push and pull Feature request: support for --insecure during apptainer push and pull Mar 19, 2024
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