private docker image with docker-compose issue

[s1rd4v3]

Hi all,

I'm having a hard time deploying my nextjs, strapi & postgress application on dockploy with docker-compose. I have an organization on github with a private monorepo. On branch push I've setup a workflow to build and publish both docker images, the strapi app and the nextjs app, against the github registry. This all works fine and as expected and I can directly use my docker-compose.yml with a reference to the images on a Portainer instance without issues. But with Dokploy I'm getting this error about being unauthorized to access a manifest.... No idea what this means to be honest since I haven't heard of those manifest in a docker context yet :). I've authorized Dokploy to access my private repo via the dedicated Settings page (Github App), in the Cluster settings I've added the github registry with my credentials, and I've additionally authenticated via Terminal on my VPS directly via docker login ghrc.io. I can successfully pull those two images with docker pull independently but just not via docker compose.

Any ideas what I'm missing?

╔══════════════════════════════════════════════════════════════════════════════╗
║                                                                              ║
║ App Name: compose-connect-1080p-matrix-991r83                                ║
║ Build Compose 🐳                                                             ║
║ Detected: 0 mounts 📂                                                        ║
║ Command: docker compose -p compose-connect-1080p-matrix-991r83 -f            ║
║ ./docker-compose.yml up -d --build --remove-orphans                          ║
║ Source Type: docker github ✅                                                ║
║ Compose Type: docker-compose ✅                                              ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝
 backend Pulling 
 frontend Pulling 
 frontend Error Head "https://ghcr.io/v2/ORGNAME/REPONAME/manifests/frontend": unauthorized
 backend Error context canceled
Error response from daemon: Head "https://ghcr.io/v2/ORGNAME/REPONAME/manifests/frontend": unauthorized
ERROR: Error: child exited with code 18: ❌

[Siumauricio]

Got it, The registry is used purely on docker swarm, not for docker compose, This is a good case where we can handle this, Because I didn't take in consideration this way like to use a private image, let's move to an issue since this is really a need!

[Siumauricio]

I created a issue #125

[Siumauricio]

@s1rd4v3 I was a long time looking for a solution to this but apparently you can not mount the authentication file from the container to the host, the way to solve it is to pass this flag with the path where the authentication json is, I made some small changes in the code that when you use the TEST REGISTRY button that is in the part where you add the registry, when you press that button and the connection is correct you will get a toaster, that means that the authentication was added correctly to the file /root/. docker/config.json, so now to be able to use that file you would have to assign this environment variable in the Enviroment Variables tab like this DOCKER_CONFIG=/root/.docker/config.json.

Note, In the new update v0.2.0 just make sure to recreate the registry and use the TEST REGISTRY please and that will be enough and also don't forget to add the env DOCKER_CONFIG=/root/.docker/config.json.

containrrr/watchtower#596

Before using the enviroment, error authenticated

After settting the env

The image is being downloaded and executed sucessfully!

Let me know if you have some questions or bugs!

[Siumauricio]

Good point, I'll add the variable by default, but can override by specifying the same variable in the env tab

[s1rd4v3]

Sounds great 🙏

[Siumauricio]

I Release the new version, let me know if its working!

[s1rd4v3]

It's working now. Thanks a lot @Siumauricio 🎉

[Siumauricio]

I'm glad that is working!!

[abdussamadbello]

@Siumauricio
Can we do the same thing for dokcer deployments?