diff --git a/.github/workflows/tasks-container-update.yml b/.github/workflows/tasks-container-update.yml
index 57660a1d27e..c4f2dbcb45e 100644
--- a/.github/workflows/tasks-container-update.yml
+++ b/.github/workflows/tasks-container-update.yml
@@ -12,7 +12,7 @@ jobs:
       pull-requests: write
       statuses: write
     container:
-      image: quay.io/cockpit/tasks
+      image: ghcr.io/cockpit-project/tasks
       options: --user root
     steps:
       - name: Set up configuration and secrets
diff --git a/HACKING.md b/HACKING.md
index 7a5e452ab55..9363482ac88 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -17,7 +17,7 @@ remote, for example with
 
 ## Setting up development container
 
-The cockpit team maintains a [cockpit/tasks container](https://quay.io/repository/cockpit/tasks)
+The cockpit team maintains a [cockpit/tasks container](https://ghcr.io/cockpit-project/tasks)
 for both local development and CI. If you can install [toolbx](https://containertoolbx.org/) or
 [distrobox](https://distrobox.privatedns.org/) on your system, it is highly
 recommended to do that:
diff --git a/test/README.md b/test/README.md
index 806f169d8ef..4967812e3d6 100644
--- a/test/README.md
+++ b/test/README.md
@@ -95,7 +95,7 @@ Pixel tests make a screenshot of a selector and compare it to a known good
 reference image. if there is a difference, the test fails and a pixel
 difference is shown.
 
-This works as our tests run in the [cockpit/tasks container](https://quay.io/repository/cockpit/tasks)
+This works as our tests run in the [cockpit/tasks container](https://ghcr.io/cockpit-project/tasks)
 which pins the browser and font rendering so repeated runs provide the same
 pixels. To generate new pixels, this tasks container must be used; your own
 browser and font rendering software might generate different results. For more