Add docker-image workflow

[symeneses]

What is this PR about?
It solves #5939

It add a workflow docker-image, The workflow get the labels and tags, build the image, test it and push it to Docker Hub. The workflow will be triggered when there are new releases.

It's needed to have the secrets with the Docker Hub user DOCKERHUB_USER and token DOCKERHUB_TOKEN.

The workflow was tested using act. The test image is in a test image where you can see the tags (latest and version) created. These tags can be modified if needed.

#DataUmbrellaPyMCSprint

...

Checklist

• [ x] Explain important implementation details 👆
• [x ] Make sure that the pre-commit linting/style checks pass.
• [ x] Link relevant issues (preferably in nice commit messages)
• [ x] Are the changes covered by tests and docstrings?
• [ x] Fill out the short summary sections 👇

[codecov]

Codecov Report

Merging #5966 (39fbf57) into main (e7d0607) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #5966      +/-   ##
==========================================
- Coverage   89.42%   89.38%   -0.04%     
==========================================
  Files          73       73              
  Lines       13292    13249      -43     
==========================================
- Hits        11886    11843      -43     
  Misses       1406     1406              

Impacted Files	Coverage Δ
pymc/distributions/continuous.py	97.89% <0.00%> (-0.10%)	⬇️
pymc/ode/ode.py	85.85% <0.00%> (ø)
pymc/ode/__init__.py	100.00% <0.00%> (ø)

[michaelosthege]

To test this, we should (temporarily) change the trigger condition to

on:
  push:

...and turn off actually pushing it.
I believe this is covered by the example here? https://github.com/docker/build-push-action#git-context

They also write that the checkout action is not needed, because the docker/build-and-push action does a git checkout automatically?

In the meantime I'll try to figure out who knows our DOCKERHUB_USER and DOCKERHUB_TOKEN, because they are not yet set as repository secrets.

[michaelosthege]

The workflow was tested using act. The test image is in a test image where you can see the tags (latest and version) created. These tags can be modified if needed.

The image appears to be private? It's asking me to log in..

[twiecki]

In the meantime I'll try to figure out who knows our DOCKERHUB_USER and DOCKERHUB_TOKEN, because they are not yet set as repository secrets.

I own the docker organization and now created and added these secrets, so this should work now. Can we test it somehow or should we just merge?

[symeneses]

They also write that the checkout action is not needed, because the docker/build-and-push action does a git checkout automatically?

I tested it without the checkout but it failed.

[symeneses]

The workflow was tested using act. The test image is in a test image where you can see the tags (latest and version) created. These tags can be modified if needed.

The image appears to be private? It's asking me to log in..

You should be able to see login in with any user. The image looks like this:

[symeneses]

In the meantime I'll try to figure out who knows our DOCKERHUB_USER and DOCKERHUB_TOKEN, because they are not yet set as repository secrets.

I own the docker organization and now created and added these secrets, so this should work now. Can we test it somehow or should we just merge?

It can be tested using act executing this command:

act release -j build-container -v

For that I changed the image name name=pymc/pymc to name=symeneses/test. Also, as my laptop is M1, while testing I had to add platforms: linux/x86_64 in the steps Build and load image and Build and push.

[twiecki]

I'm merging this, we can always keep working on it in follow-up PRs. But will this now trigger a build we can test or do we need to make a release for that?

[symeneses]

I'm merging this, we can always keep working on it in follow-up PRs. But will this now trigger a build we can test or do we need to make a release for that?

It will be triggered only by release

[twiecki]

Just cut a new release, let's see!

[twiecki]

Does not look promising https://github.com/pymc-devs/pymc/actions/runs/2676293391