Description
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
I'll get something like this:
The push refers to repository [my-registry.internal/aspnet]
2c9650081f30: Pushing [============> ] 4.417MB/18.24MB
4361eed95611: Pushing [==> ] 3.841MB/77.3MB
61d1fce9f418: Pushing [==================================================>] 8.36MB/8.36MB
9010b92c40be: Pushing [==========================================> ] 42.92MB/50.85MB
2f140462f3bc: Pushing [==================================================>] 70.14kB/70.14kB
63c99163f472: Pushing [==================================================>] 139.8kB/139.8kB
ccdbb80308cc: Pushing [==============> ] 23.41MB/82.4MB
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.