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 and document pushing to AWS ECR #65
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
@yuvipanda has this been closed by #70 ? |
I've updated the top comment on this one, as I think that it was worded a little unclearly. It's not focused on documenting how to set up on Amazon ECR as a test-case so that others have a concrete example to follow for other registries as well. |
Here is an example of providing credentials, configuring docker to use them, and then doing a |
Finally concluded that the action does indeed work with pushing to an Amazon ECR registry 🎉 I have a working example in this repo here. Note that Without this, pushing the image fails with (thanks @sgibson91 for pointing me to docker/build-push-action, this was where the quest started from) |
Description
I want to automatically build and push images to a repository that uses docker credential stores rather than username / password to log in. This is not a documented use-case of this repository, so it's unclear whether it is supported or not.
To start off, let's try getting this action to work with Amazon ECR, as this is a very common registry to use as a test case.
Benefit
This would be valuable because many container registries don't user U/P credentialing (like AWS ECR). Documenting this process for one of them would make it easier for others to understand how they could apply it to other registries.
Implementation
We could test this out by following the Amazon ECR action here:
https://github.com/aws-actions/amazon-ecr-login#usage
Tasks
Alternative approaches
Install repo2docker manually and push, which I've done in amfriesz/lpdaac_hls_tutorial#2.
The text was updated successfully, but these errors were encountered: