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
Switch from docker hub to ghcr.io (github) #2704
Comments
I think we should pull the images from docker. |
I will work on a PR. After the PR has been submitted, reviewed and merged, I will first make the 1.9 images available on ghcr.io before deleting the images in the docker org mailu. |
2705: Switch from docker.io to ghcr.io for deploying images r=mergify[bot] a=Diman0 ## What type of PR? enhancement ## What does this PR do? As we all know, docker has announced that they will stop with free docker organisations. The Mailu project used this. In about a month, the mailu docker org stops to exist and all images will be deleted. This PR modifies the CI/CD workflow (github actions) to use ghcr.io as the container registry for deployed images. The images are first build with `-build` appended to the tag. These images are also used in the test step. Only in the deploy phase, are the final tags added (as it should be). This makes sure new images are only available after the deployment step. The setup utility is updated to use `ghcr.io/mailu` as the docker_org. All references to the docker org `mailu` have been replaced with `ghcr.io/mailu` in the documentation. I confirmed via my Mailu_Fork repo that the github workflow works fine. https://github.com/Diman0/Mailu_Fork/actions/runs/4440118095 ### Related issue(s) - closes #2704 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [x] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz>
I need to migrate one installation to a new box and I am not able to pull 1.9 from anywhere. I guess for now I can try copying existing images from a working server or push them somewhere. Did you guys manage to add 1.9 images to ghcr? |
|
Weird, I was not able to pull them with just DOCKER_ORG passed. I'll check more. Thanks @nextgens! |
This does nothing
Changing it manually also does nothing |
EDIT:
To switch to the images on ghcr.io.
docker-compose down
.env
in the same folder asdocker-compose.yml
with the contents:docker-compose up -d
docker-compose ps
❗ Mailu 2.0 has been released! ❗
It is recommend to switch to Mailu 2.0. Please read https://mailu.io/2.0/releases.html before making the switch.
old post:
https://blog.alexellis.io/docker-is-deleting-open-source-images/
https://news.ycombinator.com/item?id=35166317
Docker has decided to shutdown all 'Free Team organizations'. Mailu also makes use of this. So we have to move to a different registry for the production images. Ghcr.io (github) is already used for everything but the 1.9 images.
To use it, prefix the image path with ghcr.io. E.g.
Instead of
docker pull mailu/admin:master
use:
docker pull ghcr.io/mailu/admin:master
or for testing images:
docker pull ghcr.io/mailu/admin:pr-2703
Tasks that must be done for switching:
After the switch has been made, we have to decide if we remove all images from docker. This should give a wake up call to people who never visit the website.
The text was updated successfully, but these errors were encountered: