-
Notifications
You must be signed in to change notification settings - Fork 39
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: Don't push to any registry #431
Comments
I think you're looking for #283. |
More or less, but I don't need it to be tarred either. |
@menasheh how would you use the image/layers if not TAR'd? That's the format that OCI Registries are primarily work with, can you clarify what you'd do with the non-TAR'd assets? |
@baronfel I'm using antifactory enterprise, I'm 100% certain if its using tar.gz. Also I already have composite GitHub Actions that take care of tar and upload. So if publish was supported without that it would be simple for me to integrate with my existing build process. Anyway I guess this is a minor detail cause I can always untar if I need to. The important part is not to rely on docker being installed if I want to publish without a registry configured. I'm not sure why dotnet cli wants to do everything end to end. Providing fundamental pieces would give the most flexibility for diverse deployment processes. |
Same here, just build the Docker image during publish but do not push it. Besides the the flexibility to reuse existing push build logic this allows execution of other build logic before pushing. In my case I spin up the built Docker image and execute automated system tests. |
How can I build a docker image without a manual Dockerfile, but without pushing to a registry - even local? I can handle the upload myself after.
The text was updated successfully, but these errors were encountered: