Automatic docker build and publishing

[vfdev-5]

🚀 Feature

Idea is to rebuild and publish pytorch ignite images once a new tag/release is published or a push to the master inside docker folder.

How to publish docker image:

• https://docs.github.com/en/actions/guides/publishing-docker-images#publishing-images-to-docker-hub-and-github-packages

TODO for maintainers:

• create secrets for username/tokens
• ensure that we can build apex, horovod etc on CPU-only machines

[vfdev-5]

Current state of the issue:

• we provide scripts to build and push images:
  • https://github.com/pytorch/ignite/blob/master/docker/hvd/build_all.sh
  • https://github.com/pytorch/ignite/blob/master/docker/main/build_all.sh
  • https://github.com/pytorch/ignite/blob/master/docker/msdp/build_all.sh
  • https://github.com/pytorch/ignite/blob/master/docker/push_all.sh

What remains to do:

• ensure that we can build apex, horovod etc on CPU-only machines
• create a github action which is triggered on "new tag/release is published" or "push to the master inside docker folder"
  this action should call 3 build_all.sh in parallel and finally call push_all.sh

[trsvchn]

@vfdev-5 I think I can help with this part:

create a github action which is triggered on "new tag/release is published" or "push to the master inside docker folder"

But

this action should call 3 build_all.sh in parallel and finally call push_all.sh

I'm not sure that it's possible with GH Actions: Steps in parallel?:

Not at this moment. Only jobs can run in parallel, but steps always run sequentially. I don’t know if there are any plans to ever support this.