Solved registry auth attempt fails

[BrutalBirdie]

@girish from my local machine I can login, push, pull all good.
In Cloudron I can setup the registry auth attempt fails.
Also login via shell does not work and I get this

docker login dr.domain.tld
Username: tetra.test
Password:
Error saving credentials: error storing credentials - err: exit status 1, out: `Cannot autolaunch D-Bus without X11 $DISPLAY`

[girish]

@brutalbirdie I think your issue is something else. It's related to do with the client trying to store credentials maybe to gnome key ring or something? Does https://stackoverflow.com/questions/51657060/error-saving-credentials-in-docker-login work?

edit: moved this to a separate topic, hope that's ok...

[BrutalBirdie]

@girish said in registry auth attempt fails:

edit: moved this to a separate topic, hope that's ok...

Different issue, separate topic. Ofc no problem with that

Does https://stackoverflow.com/questions/51657060/error-saving-credentials-in-docker-login work?

Funny. gnupg2 did not work but installing pass.

docker login dr.domain.tld
Username: tetra.test
Password:
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Will check tomorrow if I can use the docker registry from the app store for custom apps.

[BrutalBirdie]

@girish said in Cannot install apps from docker-registry because authentication fails:

@msbt Found the problem after much debugging. It seems there is some special code that changes the UI string depending on the client. So, the proxyAuth addon does not allow dockerode to authenticate properly.

https://git.cloudron.io/cloudron/box/-/commit/1d0ad3cb47f85b05eabb31853c8c3a585d06c2e9 is the fix. It's really just changing docker-client to docker. If you apply the patch, restart the box code and also go to Docker registry app -> Location -> Save to regenerate the nginx config.

This answers my own question.
I will try to apply the patch tomorrow.

[BrutalBirdie]

@girish Yep after applying the patch and following your steps, it's now working as expected.

If you apply the patch, restart the box code and also go to Docker registry app -> Location -> Save to regenerate the nginx config.

---

How to apply the patch? This is no git repo WTF!?

Here an example what I did.

cd /home/yellowtent/box
wget https://git.cloudron.io/cloudron/box/-/commit/1d0ad3cb47f85b05eabb31853c8c3a585d06c2e9.patch
patch -p1 < 1d0ad3cb47f85b05eabb31853c8c3a585d06c2e9.patch

The patch failed for the CHANGES file tho. But I assume with the next Cloudron update these files will be updated anyway.

[nebulon]

@brutalbirdie I guess it is easier to change those two js files manually in this case given the changes are so small. Then restart the process with systemctl restart box

[BrutalBirdie]

@nebulon sure in this case
But if someone read this topic further down the road how to apply a patch this could help him.