Module update from cmdline fails

Hi, I build some modules myself and have a problem, I hope somebody can help. The module builds, the package is created and I have a working application on one of my ns8 hosts. So far, so good. I updated the module to reflect newer docker io containers that I used. To updat ns8, the manual command (source: dev manual) should force update the module.

api-cli run update-module --data ‘{“module_url”:“ghcr.io/maja2020/ns8-photoprism",“instances”:[“photoprism2”],"force”:true}’

If I delete the module and reinstall all works fine. If i use the update command the following error occurs:

Error: initializing source docker://ghcr.io/maja2020/ns8-photoprism:latest: Requesting bearer token: invalid status code from registry 403 (Forbidden)

Searching the error leads to "unable to pull the image from ghcr.io because of a login to ghcr.io. My local machine has an active login session to github (since I need to push code) but not to ghcr.io.

What I cannot explain is why the ns8 add-module command works fine and pulls the package correctly, while the module update command fails. I can reprduce the behaviour if do a podman pull request from the commandline on my dev machine and my ns8 production server.
Anyone any idea’s on the root cause and how to solve this?

2 Likes

Maybe related:

EDIT:

I think the URL is wrong, the “ns8-” prefix isn’t needed:

api-cli run update-module --data '{"module_url":"ghcr.io/maja2020/photoprism:latest","instances":["photoprism2"],"force":true}'

2 Likes

It’s that simple… Thx. Working as expected now…

2 Likes

Considering announcing the app? The wiki is waiting for you :wink:

2 Likes

Still work to be done to complete the ns8-admin panel ui part and how to modify the application environment settings.

3 Likes