chore: Pull Safe images from GHCR instead of Docker Hub - #193
Merged
Merged
Conversation
Repoint the six Safe services in the compose files at ghcr.io/safe-global. This is the path third parties follow to self-host Safe, so it is the last place that should keep pointing at a registry the services are moving off. safe-transaction-service (x3, including docker-compose.monitoring.yml) safe-config-service safe-client-gateway-nest -> safe-client-gateway safe-wallet-web safe-events-service
Diego Pazos (diegopazosrego)
force-pushed
the
chore/ghcr-images
branch
from
September 17, 2026 10:43
11aa2d3 to
69e1de1
Compare
Moisés (moisses89)
approved these changes
Sep 17, 2026
Oluwaseyi Oluwapelumi (eniayomi)
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repoint the six Safe services in the compose files at ghcr.io/safe-global. This is the path third parties follow to self-host Safe, so it is the last place that should keep pointing at a registry the services are moving off.
safe-transaction-service (x3, including docker-compose.monitoring.yml)
safe-config-service
safe-client-gateway-nest -> safe-client-gateway
safe-wallet-web
safe-events-service