You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having the same issue as #1041 but for the 8.13.4 image this time. Airgapped install, attempting to pull docker.elastic.co/package-registry/distribution:8.13.4 returns not found: manifest unknown.
8.13.3 was also missing up until a day or so ago, but this is working now.
I can manually pull docker.elastic.co/package-registry/distribution:production, but my automation is set up to pull by version number, so I'm forced to disable it when this happens as a missing image takes down my local package registry.
Is this likely to continue happening, i.e., the docker image is unavailable when an update to the rest of the stack is released?
Cheers
The text was updated successfully, but these errors were encountered:
Hi @ceeeekay thanks for the issue. This was an issue with the release automation process around git tags and should be fixed soon. The release engineering team is on it and we will post an update once the latest Docker images are built + tagged.
Is this likely to continue happening, i.e., the docker image is unavailable when an update to the rest of the stack is released?
No, this was a one-off issue in the release process and the root cause is being fixed. This should not happen again and shouldn't be expected behavior.
Hi there,
I'm having the same issue as #1041 but for the 8.13.4 image this time. Airgapped install, attempting to pull
docker.elastic.co/package-registry/distribution:8.13.4
returnsnot found: manifest unknown
.8.13.3 was also missing up until a day or so ago, but this is working now.
I can manually pull
docker.elastic.co/package-registry/distribution:production
, but my automation is set up to pull by version number, so I'm forced to disable it when this happens as a missing image takes down my local package registry.Is this likely to continue happening, i.e., the docker image is unavailable when an update to the rest of the stack is released?
Cheers
The text was updated successfully, but these errors were encountered: