-
Notifications
You must be signed in to change notification settings - Fork 97
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
Publish image to ghcr.io #70
Comments
I agree, but I am more or less single-handedly maintaining this project in my limited free time. The issue is to refactor our long-standing scripts for build-deploy to a more modern approach. We are open to contributions or an example fork that works. It is "On the list". |
What do you mean by a more modern approach? I'd be willing to help with this. |
@pdlloyd After discussions at the Yocto summit & OEvDM last week, I'm going to take a look at this later this week. The plan is to replace the build scripts with the use of GitHub Actions such as https://github.com/docker/build-push-action as that keeps things lightweight and easy on development time. Container images will be pushed to ghcr.io as well as the Docker Hub if possible. |
The dependent containers are now available, thanks to @pbrkr crops/yocto-dockerfiles#89 |
Can you please additionally publish the image to the github container registry?
https://docs.github.com/en/actions/publishing-packages/publishing-docker-images#publishing-images-to-github-packages
This would be very useful as hub.docker.com has a rate limit off 100 / 6h for anonymous pulls.
The text was updated successfully, but these errors were encountered: