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 not sure if this is supposed to work or not, and if not, why. I have a functioning registry (thank you so much for that!) and I build and push windows images to it routinely. Now I'm trying to push a linux image (aspnet 3.1-focal aka ubuntu 20.04) to it and it seems to work (even gets part of the way through) but just hangs. For example:
docker pull mcr.microsoft.com/dotnet/aspnet:3.1-focal
docker tag mcr.microsoft.com/dotnet/aspnet:3.1-focal my-registry.internal/aspnet:3.1-focal
docker push my-registry.internal/aspnet:3.1-focal
but then it just hangs (not always at the same place). FWIW, I'm doing this on the server that's running the registry container - LTSC2019 with LCOW enabled. Pushing (the more typical) nanoserver images works flawlessly and quickly.
Is there a conceptual problem I'm missing regarding storing linux images in this registry? I would have though that the images were just layers of data, uninterpreted by the registry and that this would have worked. Or is this a bug, or something with a workaround I have yet to discover?
The goal is to build .net core images for both focal and nanoserver and store them in the same place.
Thank you again for a most helpful product.
The text was updated successfully, but these errors were encountered:
Technically it should work to store Linux images. They all look the same in a registry.
But I haven't used this registry image for a long time. Maybe there are bugfixes/improvements that my images does not have.
I'm not sure if this is supposed to work or not, and if not, why. I have a functioning registry (thank you so much for that!) and I build and push windows images to it routinely. Now I'm trying to push a linux image (aspnet 3.1-focal aka ubuntu 20.04) to it and it seems to work (even gets part of the way through) but just hangs. For example:
I'll get something like this:
but then it just hangs (not always at the same place). FWIW, I'm doing this on the server that's running the registry container - LTSC2019 with LCOW enabled. Pushing (the more typical) nanoserver images works flawlessly and quickly.
Is there a conceptual problem I'm missing regarding storing linux images in this registry? I would have though that the images were just layers of data, uninterpreted by the registry and that this would have worked. Or is this a bug, or something with a workaround I have yet to discover?
The goal is to build .net core images for both focal and nanoserver and store them in the same place.
Thank you again for a most helpful product.
The text was updated successfully, but these errors were encountered: