Move to Docker organization

[crazy-max]

I plan to archive this repository following the work I did with the Docker team on an action that will be formalized in their organization: https://github.com/docker/setup-buildx-action

There will be a total of 4 actions:

• docker/setup-buildx-action
• docker/setup-qemu-action
• docker/login-action
• docker/build-push-action

I have also created another repo to check the behavior of these actions: ci.yml / full.yml.

A real example is available on this repo.

You can already try them out and report any issues you may encounter.

[ttshivers]

In your examples, I notice you don't use any caching actions for the docker builds.

[crazy-max]

@ttshivers See https://github.com/docker/build-push-action/tree/v2#leverage-github-cache as an example

[scyto]

I only just found this solution, been looking for something like this for 2+ years. It's awesome. I implemented crazy-max's native solution first. Then found this bug so rebuilt in new docker owned variant. Their documentation is more confusing; but got it all sorted.

If anyone is interested, this is what a complete non-programmer, who had never seen this before, managed in ~6 hours - most of that was troubleshooting the weird rpc bug on push (tl;dr its random and i can't, as you all know!). This example uses the new docker workflows/actions and one of the dockerhub readme / description actions/workflows.

https://github.com/scyto/infinitude/tree/master/.github/workflows

@crazy-max sent you a thanks.
Alex

PS i had never used actions and workflows before today either...

[scyto]

In your examples, I notice you don't use any caching actions for the docker builds.

I just implemented the cache, not sure what it really buys me as even with zero dockerfile changes it rebuilds all architecture tags from the ground up every run? It didn't reduce the time when the cache was used....

[crazy-max]

v1.0.0 of docker/setup-buildx-action is now available and published to the marketplace. This action will be archived and user prompted to use the official Docker action.