New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty docker content digest causing service creation/update impossible - No 2 #676
Comments
Just ran into the same issue. Everything was fine, then servers spiked in resource usage and now I'm in this situation too |
Hi, |
This is urgent - any ideas how to fix this? |
Hello :-) It seems to be a problem with the version of GitHub Actions (Metadata, etc.). We used Docker Hub as container registry, but out of the blue I changed it to ghcr.io (GitHub Container Registry). I followed the guides Working with github packages registry and publishing and installing with github actions. Add a Registry v2 in Swarmpit
For creating a service
After Deploying you can make changes to the service and all works like expected. |
workaround is to the edit whole stack |
Hi,
we want to use swarmpit for our system, but there's an error, we don't get rid of.
Service creation failed. rpc error: code = InvalidArgument desc = ContainerSpec: "***/package-name:main@" is not a valid repository/tag
We searched the issues and there was the same issue, but no solution for this (#312)
We're using Docker Hub (private), Auth went well, swarmpit searches the Hub, shows the Repo, etc.
We tagged the package with 'latest', 'main', etc. and nothing seems to work.
We tried swarmpit v1.9, also Edge (currently v1.10-850a7f9). No changes at all.
Our Github Action is pretty simple
The
latest
for each branch is currently just a test ;-)Fun fact
If we create a stack, it can pull the image, create a service, everything is fine. But when you edit the service and toggle Auto-Deploy for example, you will run in the same error message as above.
Does anyone run in the same problem and can provide a solution for this?
All the best
Stefan
The text was updated successfully, but these errors were encountered: