microsoft / containerregistry Goto Github PK

Microsoft Artifact Registry description and related FAQ

containerregistry's Introduction

Microsoft Artifact Registry (MAR)

Microsoft Artifact Registry (also known as Microsoft Container Registry or MCR) is the primary Registry for all Microsoft Published artifacts (such as container images) that offers a reliable and trustworthy delivery of artifacts with a syndicated catalog, while maintaining the quality that customers expect from a Microsoft product offering.

For more background on MAR:

Browsing MAR Content

The discovery experience for MAR is provided through the MAR discovery UI on mcr.microsoft.com and Docker Hub.

To browse the list of repositories within MAR, visit https://mcr.microsoft.com/
To browse the list of tags, within a repository:

a. Visit https://mcr.microsoft.com/

b. Select an artifact from the catalog listing

c. Select the Tags tab to view the list of tags for that particular artifact

Additional Guidance for the Use of MAR

Providing Feedback

Please open issues to provide your feedback on usage, as well as any suggestions or concerns with MAR.

FAQ

What is the difference between MAR and MCR?

There is no difference, MAR and MCR are the same product offering.
Will the endpoints change from mcr.microsoft.com to mar.microsoft.com?

No, all endpoints will use the existing mcr.microsoft.com structure.
How does MAR work with Docker Hub?

MAR is a public registry for housing Microsoft's official artifacts (such as container images). Docker Hub is one of the official sources (in addition to https://mcr.microsoft.com) for our customers to discover official Microsoft-published container images. For further details of this integration please visit our blog.
What is the difference between MAR and ACR (Azure Container Registry)?

MAR is a public registry for housing only Microsoft's official artifacts (such as container images). ACR is a private container registry for housing our customers' container images.
Can I browse MAR?

Yes, customers can browse the MAR discovery UI at mcr.microsoft.com. Customers can view rich content like descriptions and tag listings for each artifact.
Can I Onboard new Images to MAR?

No, Given that MAR is meant to host only official Microsoft Container Images, only Internal Microsoft Product teams will be able to onboard images to the registry. Once onboarded, the images are available to all public users.

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

containerregistry's People

Contributors

Stargazers

Watchers

Forkers

rotata stevelasker klawrawkz kadahl aadaniu commops74-zz cloudmelon toddysm ossattorney bhaskers-blu-org2 taffywrinkle claudiusgonzo chenpighead richlander diodfr absing chefren briansu2004 satya-cmd rcarmonad naiteeks sonamgupta28 zcat7449 m1cal-net bulanyoso global-localhost global19-atlassian-net global19 sabinsh fabps zhouqr2000 elissandroms sundayayandele dotam99 digitalarche i-cat carlnielsen jasallen yasintasasiz mtaghi81 paulw-integrator suryamct msangapu-msft imcodder terrychang1015 amalraj7171 mr-craps gopinathravichandran dixon7832 kvamsij tatianamsnyk alonrubin2 doxingg ihvh pradeepkandel 0x06000000 weare0 vishiy msanjeewa linalakk87 reyeshl manny27nyc hjkl950217 liangtsao rameez4u balam59 rajeevek zarvd subhashsingh95 llx9 alhartkh amos0505 bobwilmes sabaripkumar k12609 edwardt iradjai dionmauricio fabriciobissaco lakshmimeghana9 sozturk88 bbishopmsft test-mass-forker-org-1 ariel11 yaqisun7 thcpatrescz pombredanne

containerregistry's Issues

mcr.microsoft.com is down

I'm sure this isn't the right place to report this, but mcr.microsoft.com is down. Is there a way to check its status and/or report an error? status.azure.com has an entry for "Container Registry" but it's not clear if this is the same thing. Any guidance you could provide would be appreciated.

Here's what goes wrong:

$ docker pull mcr.microsoft.com/dotnet/core/sdk:3.1
Error response from daemon: Get https://mcr.microsoft.com/v2/: Service Unavailable

I got this error running locally on macOS. Restarting the docker daemon had no effect. Pulling the same image in a docker build running on GitHub Actions produces the same error.

Question: Is There a Way to Get Notify/Email/Webhook If Offical Image is Updated?

@denhsu commented on Thu Jul 04 2019

We have our application image store in Azure Container Registry and it uses Microsoft official image "microsoft/aspnet:4.7.1-windowsservercore-ltsc2016".

Is it possible to notify us/email/webhook when image is updated in this repo? For example, automatically trigger a build in our Azure DevOps to rebuild the application to take latest OS image.

Thanks!

@MichaelSimons commented on Tue Jul 09 2019

I am not aware of anything. If you are able to utilize ACR Tasks, they have support for this scenario as described here.

Moving to https://github.com/microsoft/ContainerRegistry since this is an MCR specific question.

PS C:\Users\Administrator> docker pull mcr.microsoft.com/windows/servercore:ltsc1809

I am trying to use docker run to download an image and get the error below
PS C:\Users\Administrator> docker pull mcr.microsoft.com/windows/servercore:ltsc1809
docker : Error response from daemon: Get https://mcr.microsoft.com/v2/: net/http:
request canceled while waiting for connection (Client.Timeout exceeded while awaiting
headers)

AzureMonitor missing on MCR

Hey,

I'm having problems while executing bash enable-monitoring.sh --resource-id $azureArcClusterResourceId

Error says
Error: mcr.microsoft.com/azuremonitor/containerinsights/preview/azuremonitor-containers:2.8.2: not found
If I go to https://hub.docker.com/publishers/microsoftowner I don't see any image for containerinsights

I'm following the next guide to achieve Azure monitoring with Azure ARC

https://docs.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-enable-arc-enabled-clusters?toc=/azure/azure-arc/kubernetes/toc.yml

Has the images been removed from the registry?

How to install ReverseForwarders on nanoserver container?

How to install ReverseForwarders on nanoserver container?
I need the missing dlls in nanoserver.

Is the microsoft container registry subject to dockerhub throttling?

Hello, as you probably know, dockerhub has recently begun throttling pulls.

Since the microsoft container registry has it's "discovery mechanism" through dockerhub, will it be subjected to dockerhub throttling? I mainly ask because it seems that the rate-limiting applies to pulling manifests from dockerhub, not just the image itself.

Your build tool has a typo: rootfS

Whatever is producing these images has a typo in the config file generation.

Looking at the config file for:

mcr.microsoft.com/windows/iotcore@sha256:e6c7080bf78f50b8382c5a30dab8ef51c6426004a9c1749136c11f507d503e76

$ curl -s -L https://mcr.microsoft.com/v2/windows/iotcore/blobs/sha256:5466c718be1bbae9580c4ff3f9adf2eb8282114b795cf51b09a2d69e9822aabd | jq . | grep root
  "rootfS": {

That S in rootfS is capitalized, but it should probably be rootfs per the spec and specs-go.

As far as I know, this isn't a problem because most container runtimes are written in go, which has case-insensitive json Unmarshalling:

To unmarshal JSON into a struct, Unmarshal matches incoming object keys to the keys used by Marshal (either the struct field name or its tag), preferring an exact match but also accepting a case-insensitive match.

In general, though, JSON is case sensitive, so you're likely to run into issues with other languages.

where are the logs?

I can't see logs!
no logs inside the container, neither in the docker dashboard

docker

Cannot pull some of the Nanoserver and WindowsServerCore image tags

When I try to download a lot of the Windows Server Core and Nano Server images, I get the below error.

Error
Error response from daemon: manifest for microsoft/windowsservercore:latest not found.

Same issue with mcr.microsoft.com images/tags

Same issue as the below
docker/for-win#3761

Default code page in Server Core Insider images

It seems that the default code page on 10.0.19008.1 and 10.0.19023.1 is 65001, preventing CMake from identifying C/CXX compiler.

CMakeError.log:

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler:  
Build flags: 
Id flags:  

The output was:
1
Microsoft (R) Build Engine version 12.0.40629.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 3/22/2020 12:21:50 PM.
Project "C:\share\opencv-3.4.9\build\CMakeFiles\3.16.5\CompilerIdCXX\CompilerIdCXX.vcxproj" on node 1 (default targets).
PrepareForBuild:
  Creating directory "Debug\".
  Creating directory "Debug\CompilerIdCXX.tlog\".
InitializeBuildStatus:
  Creating "Debug\CompilerIdCXX.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
ClCompile:
  C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\x86_amd64\CL.exe /c /nologo /W0 /WX- /Od /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"Debug\\" /Fd"Debug\vc120.pdb" /Gd /TP /errorReport:queue CMakeCXXCompilerId.cpp
  CMakeCXXCompilerId.cpp
CMakeCXXCompilerId.cpp : fatal error C1001: An internal error has occurred in the compiler. [C:\share\opencv-3.4.9\build\CMakeFiles\3.16.5\CompilerIdCXX\CompilerIdCXX.vcxproj]
  (compiler file 'f:\dd\vctools\compiler\cxxfe\sl\p1\c\p0io.c', line 2807)
   To work around this problem, try simplifying or changing the program near the locations listed above.
  Please choose the Technical Support command on the Visual C++ 
   Help menu, or open the Technical Support help file for more information
Done Building Project "C:\share\opencv-3.4.9\build\CMakeFiles\3.16.5\CompilerIdCXX\CompilerIdCXX.vcxproj" (default targets) -- FAILED.

Build FAILED.

"C:\share\opencv-3.4.9\build\CMakeFiles\3.16.5\CompilerIdCXX\CompilerIdCXX.vcxproj" (default target) (1) ->
(ClCompile target) -> 
  CMakeCXXCompilerId.cpp : fatal error C1001: An internal error has occurred in the compiler. [C:\share\opencv-3.4.9\build\CMakeFiles\3.16.5\CompilerIdCXX\CompilerIdCXX.vcxproj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.76

dotnet core images are not working after the update on 29.07

Since the images update yesterday, I cannot build any image for my code (.Net core 3.1). Error message and full logs can be found under my StackOverflow question

Hope for quick help, since we are totally blocked in the project!

Outstanding CVE in MCR image used for MLOPS

Trivy found a high CVE vulnerability in the latest python image used for MLOPS (mcr.microsoft.com/mlops/python:latest). Could a new patched version be published by Microsoft?

Is there perhaps a link to the Dockerfile so we can build the image directly in our pipeline?

Total: 1 (HIGH: 1, CRITICAL: 0)

+----------------+------------------+----------+-------------------+---------------+---------------------------------------+
|    LIBRARY     | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                 TITLE                 |
+----------------+------------------+----------+-------------------+---------------+---------------------------------------+
| linux-libc-dev | CVE-2020-28374   | HIGH     | 4.4.0-197.229     | 4.4.0-200.232 | kernel: SCSI target (LIO) write       |
|                |                  |          |                   |               | to any block on ILO backstore         |
|                |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2020-28374 |
+----------------+------------------+----------+-------------------+---------------+---------------------------------------+

Provide the ability to get image size info without pulling images.

I have been asked a number of times by the .NET customers how to get the image sizes (compressed) after moving to MCR. It seems like this is something MCR should be exposing for our customers. I acknowledge the Docker Hub mechanism was flawed in that it was deceptive for multi-platform tags.

Example inquiry:
From dotnet/dotnet-docker#967 (comment) by @jonathann92
In docker hub I used to be able to see a "tags" columns and it would have all the previous tags and the size of the docker file.

TLS error access denied when trying to pull images from cdn.mscr.io endpoint

Hi,

We've been using the official microsoft images for our project that we are converting to use containers, and they were working a few months back. An example image that we are using is "mcr.microsoft.com/dotnet/core/sdk:3.1". However, some of our developers started running into a problem (I believe it was in Februrary initially) where we were getting access denied when trying to pull. when we try to pull the hello-world image from the "cdn.mscr.io" endpoint in https://github.com/microsoft/containerregistry/blob/master/client-firewall-rules.md, we get the same access denied error:

error pulling image configuration: Get https://mcrneu0.cdn.mscr.io/791e7ca5469f40b1b54c65b23e5dbde2-qgy0s4qedy//docker/registry/v2/blobs/sha256/09/095f049ec3a4c206f052648375b06599ce9d4332283bfd44ee99180c08df80f4/data?P1=1584975330&P2=1&P3=1&P4=jHPUhkNwRchm0jNoB4UjwQUNIAXMiZOtfVlvnec6bUs%3D&se=2020-03-23T14%3A55%3A30Z&sig=38Yi7vguA9F9jeX5kiuYxy4yIARQ50E0byn%2BakcA33w%3D&sp=r&sr=b&sv=2016-05-31&regid=791e7ca5469f40b1b54c65b23e5dbde2: remote error: tls: access denied

When the endpoints for the images were moved to the ".data.mcr.microsoft.com" the pulling started to work for us, but now that the change was rolled back we are now getting the access denied error again.

Other things to note:

We are using Linux container in docker-desktop
A couple of developers machines can successfully pull the images, but they have the same setup, and corporate firewall/antivirus etc. installations.

We've tried to identify whats causing it, but haven't had much success.

We've checked our firewall settings and they are the same across developers,
We've tried fresh installs of docker desktop as well.
We've tried disconnecting from the corporate network and we still get the same error.
Resetting SSL certificates and doing a direct curl to the endpoint rather than going through docker provides the same error too.

Is there anything else we could try (or a setup step we've missed?), or could there be an issue with the endpoint?

Thanks,
Mike

Typo in Readme

"ACR is a private container Registry for housing Our customers container Images" - should have an apostrophe: "Our customers' container images".

Can't pull images when running in Containers for Windows

Copied from dotnet/dotnet-docker#992 by @francoisdutoit

Steps to reproduce the issue

On Windows 10 - Switch to Containers for Windows

Expected behavior

Pull .net Core images from DockerHub : docker pull mcr.microsoft.com/dotnet/core/sdk

Actual behavior

Error:
read tcp 192.168.88.229:2897->204.79.197.219:443: wsarecv: An existing connection was forcibly closed by the remote host.

Additional information (e.g. issue happens only occasionally)

When switching to Linux containers - images pull down without an issue

Output of `docker version`

Client: Docker Engine - Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:31 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:28:48 2019
OS/Arch: windows/amd64
Experimental: false

Output of `docker info`

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 18.09.2
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 17134 (17134.1.amd64fre.rs4_release.180410-1804)
Operating System: Windows 10 Pro Version 1803 (OS Build 17134.648)
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 15.96GiB
Name: FrancoisDesktop
ID: 3BZN:MCQK:E4YF:JHFQ:45A5:5NQS:7EGG:Q7AF:R4AK:RWF5:GR5U:SOEN
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: -1
Goroutines: 26
System Time: 2019-03-17T06:32:46.5001332+02:00
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

@MichaelSimons commented on Mar 18

@francoisdutoit - Can you pull any images from mcr.microsoft.com (e.g. docker pull mcr.microsoft.com/windows/nanoserver:1809)?

@rotata - Do you know anything about this?

@francoisdutoit commented on Mar 18

@MichaelSimons - I am able to pull the Microsoft images for Linux - so when Docker is running in Containers for Linux - all is well .When I however switch over to Containers for Windows I am unable to pull the images.

@asmichi commented 25 days ago

https://twitter.com/asm_ichi/status/1124535074429366273

read tcp 192.168.1.65:27527->204.79.197.219:443: wsarecv: An existing connection was forcibly closed by the remote host.

I experienced the same problem. It seems to me the same issue as moby/moby#33667.

TL;DR: Yesterday pull from 204.79.197.219 (winlayers.cdn.mscr.io) failed from a Japan East Azure VM. No problem from a West US VM.

Yesterday I tried to docker pull mcr.microsoft.com/dotnet/framework/runtime:4.7.2-windowsservercore-ltsc2019 more than 10 times but all attempts resulted in the same error.

I created an Azure VM in the Japan East region and tried the pull command. The command failed with a slightly different error (I forgot the details). Then I tried the pull command from a VM in the West US region and it pulled the image with no error. (Probably connection speed matters??)

Around 2019-05-04 02:00 PST, suddenly the server came back good and I succeeded in docker pull mcr.microsoft.com/dotnet/framework/runtime:4.7.2-windowsservercore-ltsc2019 with no error.

Seems to me that sometimes the CDN server (204.79.197.219, winlayers.cdn.mscr.io) goes wrong for a while, then comes back working.

Hope this helps Microsoft folks to identify the root problem.

~~A test script derived from moby/moby#33667: Test-cdn.mscr.ps1.txt~~
Ignore this script; for some reason connections made by this script seem stable. Please just try docker pull.

@asmichi commented 25 days ago

Missing metadata for multiarch images

Seems there is a problem with the current MCR implementation if you try to cache it trough a system like Artifactory:

Debugging the registry calls you potentially would need to do as a docker daemon:

curl -v -L https://mcr.microsoft.com/v2/_catalog
curl -v -L https://mcr.microsoft.com/v2/windows/nanoserver/tags/list
curl -v -L https://mcr.microsoft.com/v2/windows/nanoserver/manifests/1809-amd64

This does work fine:
All calls will be forwarded to the CDN (https://mcrflowprodcentralus.data.mcr.microsoft.com/mcrprod/windows/nanoserver) and get the requested content:

{
   "schemaVersion": 1,
   "name": "windows/nanoserver",
   "tag": "1809-amd64",
   "architecture": "amd64",
   "fsLayers": [
      {
         "blobSum": "sha256:a11c4ca8f1ba16b6e1395d4523be2215bd0871c2e3e4695b9f2b87bd7472be52"
      }
   ],
   "history": [
      {
         "v1Compatibility": "{\"architecture\":\"amd64\",\"config\":{\"user\":\"ContainerUser\",\"cmd\":[\"c:\\\\windows\\\\system32\\\\cmd.exe\"]},\"created\":\"2021-02-26T16:47:31.545+00:00\",\"id\":\"d36ddcc92c9d24dd0c412013eb727aed32aa248cf214e01a79354dbe6fc2d850\",\"os\":\"windows\",\"os.version\":\"10.0.17763.1817\",\"rootfS\":{\"type\":\"layers\",\"diff_ids\":[\"sha256:fb9c5a79707ee6af09795e104e283faa4bb833ee5f4d6a6d83abfec6f85f7df4\"]}}"
      }
   ],
   "signatures": [
      {
         "header": {
            "jwk": {
               "crv": "P-256",
               "kid": "2UVQ:DXQN:GVI3:357B:ASYQ:KNLA:MZPR:LQA4:LS3P:5GAV:QUOB:XFFO",
               "kty": "EC",
               "x": "RedTOWj5xtiW4ULQ6031fJ9v5rJJGet7gGjlT839NPg",
               "y": "jMctkpWXG0Rv5j3jnWM6D4q9fOZf2tFHzqmROmaB7nQ"
            },
            "alg": "ES256"
         },
         "signature": "6uivwRPP-YEBQeiilZ8xUrmSB3sk55UDIY3_poKs_s38sBhEfzSkFA228BqJsK34b6MDHO6QV79k4-oP2OXD7w",
         "protected": "eyJmb3JtYXRMZW5ndGgiOjcyOSwiZm9ybWF0VGFpbCI6IkNuMCIsInRpbWUiOiIyMDIxLTAzLTEwVDE2OjU4OjE5WiJ9"
      }
   ]

If you try the same for a multiarch image like 20H2 - the redirect is broken - no link to the CDN gets returned:

curl -v -L https://mcr.microsoft.com/v2/windows/nanoserver/manifests/20H2
curl -v -L https://mcr.microsoft.com/v2/windows/nanoserver/manifests/20H2-KB5000802
curl -v -L https://mcr.microsoft.com/v2/windows/nanoserver/manifests/10.0.19042.867
...

Output:

{"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest  is not found"}]}

Pulling images from MCR is Slow

The pulling of images from MCR has slowed down considerably in the past two days.
Previously it would take a max of 10-15 minutes to download a windowsservercore image, however since then it has been taking over an hour and still not completing download.
This has been replicated on Azure DevOps Microsoft hosted agents, as well as two PCs in different locations.
To replicate: docker pull mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-1909

Python package sympy missing from onnxruntime-training

The package is required by this example,
https://github.com/microsoft/onnxruntime-training-examples/blob/4dae9249b75174a2b7f13012138831063cd14794/nvidia-bert/ort_addon/run_pretraining_ort.py#L40

To reproduce, run the following. latest has the same issue.

$ docker run --rm -it mcr.microsoft.com/azureml/onnxruntime-training:0.1-rc3.1-openmpi4.0-cuda10.2-cudnn8.0-nccl2.7-for-bert
root@81aac0b74186:/workspace# python
Python 3.7.3 (default, Mar 27 2019, 22:11:17)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from onnxruntime.training.checkpoint import experimental_state_dict, experimental_load_state_dict
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/conda/lib/python3.7/site-packages/onnxruntime/training/__init__.py", line 9, in <module>
    from .orttrainer import ORTTrainer, TrainStepInfo
  File "/opt/conda/lib/python3.7/site-packages/onnxruntime/training/orttrainer.py", line 13, in <module>
    from onnxruntime.tools.symbolic_shape_infer import SymbolicShapeInference
  File "/opt/conda/lib/python3.7/site-packages/onnxruntime/tools/symbolic_shape_infer.py", line 10, in <module>
    import sympy
ModuleNotFoundError: No module named 'sympy'

IP seemingly hardcoded into layer

I cannot download the image corresponding to dotnet/sdk because one of the layers, corresponding to windows/nanoserver (sha starts with e4800) seems to have the address for mcr.microsoft.com hardcoded as the tcp address 13.69.64.80. Since the certificate does not correspond with the hardcoded address, I get security warnings even when trying to access the address via https on the browser. Because of this, the corporoate firewall denies access to the address.

The issue also shows up in the Even Viewer, as an "Error initiating layer download", with the full download address (including sha) and the text "dial tcp 13.69.64.80:443: connectx" failed.

The pull is successful against Docker/Linux containers.

Container failed during run: build. No retries remaining.

Hey guys,

We are seeing an intermittent issue on the MCR. We originally thought it was an Oryx issue, but it seems to be breaking at the docker pull stage.

See.
microsoft/Oryx#602
For more information.

.NET Core SDK 3.1 Debian 10 images are throwing image configuration errors I/O timeout

I tried yesterday and again today to pull and use the Debian 10 '3.1.100' SDK image and get i/o timeout errors pulling image configuration. The 3.0.100 image reference does not do this.

Error:
error pulling image configuration: Get https://mcreus0.blob.core.windows.net/aba285c624a04409823b708c7a50e7b9-jttfjm99vo//docker/registry/v2/blobs/sha256/98/9817c25953a8ede59da1b397aa096c5ba269bbd969f55f1819393dda35f9d19f/data?se=2019-12-06T22%3A24%3A25Z&sig=n9whbNNyggFZrjyz9yyFU60hF3bgyf4yYno%2FVqpsZzM%3D&sp=r&sr=b&sv=2016-05-31&regid=aba285c624a04409823b708c7a50e7b9: dial tcp: lookup mcreus0.blob.core.windows.net on 192.168.65.1:53: read udp 192.168.65.3:43777->192.168.65.1:53: i/o timeout

Image reference being used is:

FROM mcr.microsoft.com/dotnet/core/sdk:3.1.100

This is using VSCode remote containers with Docker Desktop. I just now switched my docker file back to:

FROM mcr.microsoft.com/dotnet/core/sdk:3.0.100

and it fired right up.

Anyone else run into this or know what's going on?

.net core 2.0 base image is not found in dockerhub

.Net Core 2.0 base image has been used in docker file like below.

FROM microsoft/aspnetcore

Docker throws the below error while trying to fetch the base image from the docker hub.

**> [internal] load metadata for docker.io/microsoft/aspnetcore:latest:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed**

I have tried to find the base image of the microsoft/aspnetcore. I couldn't find it in the docker hub.

Is that mean Microsoft stopped the support of the .net core 2.0 base image?

https://hub.docker.com/r/microsoft/aspnetcore-build/

mcr.microsoft.com error pulling aspnet image

@dave-yotta commented on Tue Apr 06 2021

CI got this over the weekend - this probably isn't the right place to report this, but I'm out of ideas - I guess you'll have to forward this to your azure service provider there 🤔 (I tried looking for past incidents in the azure status page, but couldn't find it...)

#3 ERROR: failed to copy: httpReadSeeker: failed open: unexpected status code https://mcr.microsoft.com/v2/dotnet/core/aspnet/blobs/sha256:fe3a4716eba4304fdb3b6a63fd0e54aa9c6c8519f9d1ba2f67a043679dd2f64a: 500 Internal Server Error

Slow download of the image from container registries

Hello,

we are running hybrid (Win+Linux) Docker Swarm. We also span the whole cluster across multiple regions (today WEU and SAN). All nodes are VMs in Azure.

All primary infrastructure was established and has been operated in WEU. Mainly (and this is relevant in this case) the container registries ([ourregistry].azurecr.io).

The problem is since the last week (and not internal changes in docker infrastructure) we have been facing extremely slow docker pulls in SAN nodes (pulling from WEU in the case of our own images). Pulling from mcr.microsoft.com (e. g. pull mcr.microsoft.com/businesscentral/onprem) runs really fast, the same way as it was in the case of pulling from [ourregistry].azurecr.io.

We decided to enable geo-replicated container registries, everything was synced to SAN successfully but we don't see any performance impact. It looks like all layer pulls continue to use WEU registries.

Not sure what nslookup should return for [ourregistry].azurecr.io but it returns WEU resources as far as I can see (but maybe this isn't relevant).

Linux nodes in SAN we able to pull also from [ourregistry].azurecr.io our linux images fine without any impact. I haven't been testing yet to see if they pull from WEU or SAN (which should be now extremely fast).

I would be grateful for any information.

Kubernetes cluster containers getting destroyed after migration to mcr.microsoft.com/dotnet/core/aspnet:3.1

With recent migration of our app from microsoft/aspnetcore:2.0 to mcr.microsoft.com/dotnet/core/aspnet:3.1

We observed automatic decommission of the containers for minute or so and they getting restored, we are using nginx as the api gateway. And because of this outage we are getting increased 502 errors.

Everything was ok till the migration.

Can we optimize download speed in mainland China

Copied from dotnet/dotnet-docker#1269 by ZhangGaoxing

Steps to reproduce the issue

Every time I pull a image from mcr.microsoft.com, the speed is very slow(about 200k/s). It's painful
☹. Other products download speed of .NET are normal, such as direct from .NET homepage download installation package.

Using "mcr.microsoft.com/mssql/server:2019-latest" - Docker build hangs on 'xplog70.dll' version 'xxx'

System Information:
OS: macOS Catalina 10.15.7
Docker Image: mcr.microsoft.com/mssql/server:2019-latest

Context:
After updating my old DockerFile FROM microsoft/mssql-server-linux:2017-latest
to the newer... FROM mcr.microsoft.com/mssql/server:2017-latest

My build is stuck on this Terminal message and never completes:
cfml_1 | WARNING: org.xerial's sqlite-jdbc is not loaded. cfml_1 | Please provide the jar on your classpath to parse sqlite files. cfml_1 | See tika-parsers/pom.xml for the correct version.
database_1 | 2021-07-19 21:34:50.58 spid51 Using 'dbghelp.dll' version '4.0.5' 2021-07-19 21:36:32.70 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 2021-07-19 21:36:32.79 spid51 Using 'xplog70.dll' version '2017.140.3401' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
cfml_1 | [INFO ] runwar.context: Jul 19, 2021 22:38:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 19, 2021 23:45:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 00:52:43 AM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 02:26:11 AM Information [scheduler-2] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 05:47:17 AM Information [scheduler-1] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 10:59:59 AM Information [scheduler-0] - Run Client Storage Purge

Questions:

Why is there such a long delay?
How can we fix it to get this build to finish?
Is this an issue with the docker image or the JDBC driver?
Is this a MacOS specific problem?

Others seem to be having the issue ~ See reference here: microsoft/mssql-docker#554
NOTE: I also posted this same issue on microsoft /mssql-docker repository ~ here: microsoft/mssql-docker#703 ~ as well as the xerial/sqlite-jdbc repository ~ here: xerial/sqlite-jdbc#632

Currently unable to get my Dev environment working until there is a solution.
Any feedback or insight welcome.

Pull-through cache for mcr.microsoft.com is not working

Copied from dotnet/dotnet-docker#1434 by @dngcsc

Steps to reproduce the issue

Create a local docker registry that acts as pull-through cache for mcr.microsoft.com:

docker-compose.yml

version: '3'
services:
  mcr:
    image: registry:2.6.2
    ports:
     - "5003:5000"
    volumes:
     - ./registry/conf/mcr-mirror-config.yml:/etc/docker/registry/config.yml

mcr-mirror-config.yml

version: 0.1

# other fields omitted

proxy:
  remoteurl: https://mcr.microsoft.com

Change docker daemon to use http://localhost:5003 as registry mirror
docker pull mcr.microsoft.com/dotnet/core/sdk:3.0-alpine

Expected behavior

sdk:3.0-alpine is cached in mcr registry

Actual behavior

mcr registry is empty

Additional information (e.g. issue happens only occasionally)

Copied from dotnet/dotnet-docker#1434 (comment) by @mthalman

It's not clear from the pull through cache documentation whether this is even intended to be supported for registries other than Docker Hub. Regardless, this issue would be more appropriate for the MCR repo since it's a function of the registry functionality, not the .NET Docker images themselves.

An existing connection was forcibly closed by the remote host

Copied from microsoft/dotnet-framework-docker#376 by @arnigunnar

I am trying to run this command docker pull mcr.microsoft.com/dotnet/framework/runtime:4.7.2-windowsservercore-ltsc2019, but using the console, I always get an error. read tcp 10.44.103.63:59824->204.79.197.219:443: wsarecv: An existing connection was forcibly closed by the remote host.. There are 4 layers to the image, and when I am running the command, it starts downloading all four, completes the last two, but the first two (1.408GB and 514MB) the console starts downloading a few times but always ends up failing.

I have tried building through VS2019 as well with a DOCKERFILE pointing to this image, that also fails.

Full results:

65014b3c3121: Downloading [==================================================>]  1.522GB/1.522GB
02a4c14ecf32: Downloading [==================================================>]  529.5MB/529.5MB
1477e74c02fd: Download complete
f5debc34d550: Download complete
read tcp 10.44.103.63:59910->204.79.197.219:443: wsarecv: An existing connection was forcibly closed by the remote host.

Does anyone have any suggestions for me?

Outstanding CVEs in MCR images used in AKS

Looks like certain security risks published in CVEs (can be queried at https://nvd.nist.gov/vuln) are lurking in some MCR images for AKS components. Below is a Twistlock scan result:

mcr.microsoft.com	oss/kubernetes/hyperkube	v1.16.13-hotfix.20200824.1	sha256:46867bf7db870835cdfb6cd313a31ac01586e480627a93fd52f7c9d26fdce3db	debian-buster	29		CVE-2020-1472
mcr.microsoft.com	azuremonitor/containerinsights/ciprod	ciprod11092020	sha256:937c505c27dfcc4d8199f9280be5dc7c4cf33ba6893547f89dbf37160be3f184	Ubuntu-bionic	29		CVE-2020-1971
mcr.microsoft.com	aks/hcp/hcp-tunnel-front	v1.9.2-v3.0.20	sha256:7ddd7d32eeb3f9200c24dc0a232106fb93d3b237fc280351423185a28aa9dad6	Ubuntu-bionic		CVE-2020-1971
mcr.microsoft.com	oss/calico/node	v3.8.9.1	sha256:a367c0e1361467aa01b0eddf1ac568f102f321f955c66300ce455e13ced83563	debian-buster	29		CVE-2020-1971

Is there a routine for continuous vulnerability checks and plan on shooting them down?

Provide Container Digest without having to pull image

As part of our processes we need to have some kind of verification that matches a downloaded container with one that exists remotely, the digest fills this, however I can't find any way to view the digest on docker hub, or otherwise remotely.

Many other images have their digests available on the docker hub page such as alpine However none of the Microsoft ones do. I'm specifically looking at the dotnet sdk for nanoserver 1809

Is there a way to view digests before the image is downloaded, and if not can one be made available.

aqua scan reported an issue in mcr.microsoft.com/dotnet/sdk:5.0

error NETSDK1064: Package DnsClient, version 1.2.0 was not found

When building a docker image and pulling mcr.microsoft.com/dotnet/core/sdk:3.1 an error is thrown. Note this is also breaking on Elastic Beanstalk when trying to deploy a new version. This build was working two months ago.

usr/share/dotnet/sdk/3.1.201/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error NETSDK1064: Package DnsClient, version 1.2.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions. [/app/myApp.csproj]
The command '/bin/sh -c dotnet publish -c Release -o out' returned a non-zero code: 1

dockerfile -

FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
WORKDIR /app

COPY *.csproj ./
RUN dotnet restore

COPY . ./
RUN dotnet publish -c Release -o out

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1
WORKDIR /app
COPY --from=build-env /app/out .
EXPOSE 5000
ENTRYPOINT ["dotnet", "myApp.dll"]

Error Log from AWS EB -

Application deployment failed at 2020-04-12T04:58:20Z with exit status 1 and error: Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03build.sh failed.

cat: Dockerrun.aws.json: No such file or directory
cat: Dockerrun.aws.json: No such file or directory
cat: Dockerrun.aws.json: No such file or directory
3.1: Pulling from dotnet/core/sdk
Digest: sha256:cad1f51e65af52e5551e5182b163326c8fceca93d0dbb9e8de8d85b95748e4e2
Status: Image is up to date for mcr.microsoft.com/dotnet/core/sdk:3.1
Successfully pulled mcr.microsoft.com/dotnet/core/sdk:3.1
Sending build context to Docker daemon 9.972MB
Step 1/11 : FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
---> 597ba2726813
Step 2/11 : WORKDIR /app
---> Using cache
---> 68651d922492
Step 3/11 : COPY *.csproj ./
---> Using cache
---> 114b6f8c3b96
Step 4/11 : RUN dotnet restore
---> Using cache
---> 23d6f511441d
Step 5/11 : COPY . ./
---> Using cache
---> 5ed579d49642
Step 6/11 : RUN dotnet publish -c Release -o out
---> Running in 4434565a6968
Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

Restore completed in 156.69 ms for /app/BacktraderDataApi.csproj.
/usr/share/dotnet/sdk/3.1.201/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error NETSDK1064: Package DnsClient, version 1.2.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions. [/app/BacktraderDataApi.csproj]
The command '/bin/sh -c dotnet publish -c Release -o out' returned a non-zero code: 1
Failed to build Docker image aws_beanstalk/staging-app, retrying...
Sending build context to Docker daemon 9.972MB
Step 1/11 : FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
---> 597ba2726813
Step 2/11 : WORKDIR /app
---> Using cache
---> 68651d922492
Step 3/11 : COPY *.csproj ./
---> Using cache
---> 114b6f8c3b96
Step 4/11 : RUN dotnet restore
---> Using cache
---> 23d6f511441d
Step 5/11 : COPY . ./
---> Using cache
---> 5ed579d49642
Step 6/11 : RUN dotnet publish -c Release -o out
---> Running in 4c6139bea64b
Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

Restore completed in 109 ms for /app/BacktraderDataApi.csproj.
/usr/share/dotnet/sdk/3.1.201/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error NETSDK1064: Package DnsClient, version 1.2.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions. [/app/BacktraderDataApi.csproj]
The command '/bin/sh -c dotnet publish -c Release -o out' returned a non-zero code: 1
Failed to build Docker image aws_beanstalk/staging-app: ximum path length restrictions. [/app/BacktraderDataApi.csproj]
The command '/bin/sh -c dotnet publish -c Release -o out' returned a non-zero code: 1. Check snapshot logs for details.

Windows server 2004 has IIS application pool connection limit of 10

Hi,

In our docker build we changed our base windows image from 1809 to mcr.microsoft.com/windows:2004
After this our application(on IIS) runs into timeout under a minimal load, no connection can be established.
Analyzing w3wp dump gave us a hint that the cause maybe the max connection count of 10 per IIS application pool. As seen in the screenshot the number stopped increasing at 10. In 1809 we had over 70 connections.
This is somehow very similar to the limit of 10 for Desktop Windows version.
This problem did not occurred while testing with mcr.microsoft.com/windows/servercore:2004 . The connection count went over 20. We cannot use servercore version due missing functionality.

FYI As a host windows version we use Azure OS image sku: datacenter-core-2004-with-containers-smalldisk

Thanks

Certificate Issue

When I try to pull a docker image from MCR I get the following error.

sudo docker pull mcr.microsoft.com/dotnet/core/aspnet:2.2.7-bionic
Error response from daemon: Get https://mcr.microsoft.com/v2/: x509: certificate is valid for *.mcr.microsoft.com, not mcr.microsoft.com

mcr.microsoft.com/azure-cli:2.0.72 missing azcopy

Hi All,

It seems azure-cli image, and azure cli shells out to azcopy for some commands, however this isn't in the docker image.

Starting script execution via docker image mcr.microsoft.com/azure-cli:2.0.72
This command is in preview. It may be changed/removed in a future release.
WARNING: Azcopy command: ['/root/bin/azcopy', 'sync', 'dist', 'https://****.blob.core.windows.net//?se=*****&sp=rwdlacup&sv=2018-03-28&ss=b&srt=sco&sig=*****', '--delete-destination', 'true']
ERROR: The command failed with an unexpected error. Here is the traceback:

ERROR: [Errno 2] No such file or directory: '/root/bin/azcopy': '/root/bin/azcopy'
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)

I've gotten these logs from using the github actions 'Azure cli', as was wanting to use microsoft supplied actions for uploading blobs. This seemed the most reasonable approach without relying on third parties.

20H2 tags missing for windows/servercore/iis

We're updating our build pipelines to prep for 20H2 and found that the windows/servercore/iis repository has images tagged as 2009, while all other repositories that we use are tagging as 20H2. As far as I can tell, the 20H2 images in other repositories are the most updated ones and 20H2 is the preferred nomenclature.

3.1.1-nanoserver-1803 for ASP.NET Core Runtime is not available

Hi,

i could not find 3.1.1-nanoserver-1803 for ASP.NET Core Runtime. I am not sure if it is intentional.
https://hub.docker.com/_/microsoft-dotnet-core-aspnet/
https://mcr.microsoft.com/v2/dotnet/core/aspnet/tags/list

If it is not supported, Where can i see compatibility matrix for same?

How can I change initial database COLLATION?

Default COLLATION is SQL_Latin1_General_CP1_CI_AS, how to change it?

Alpine 3.14.0 or 3.13.5 image in .NET Runtime Dependencies

Hi folks.

I couldn't find alpine 3.14.0 or 3.13.5 version in https://hub.docker.com/_/microsoft-dotnet-runtime-deps/ .
I think the latest is 3.13.4.

I'm wondering if there is any short-term plan to include a new image in the repository mcr.microsoft.com/dotnet/runtime-deps with alpine 3.14.0 or 3.13.5 version or if is there any workaround or recommendation you can provide?

Microsoft container images discovery experiences on DockerHub

Readme points to the blog post which describes the Microsoft container discovery experiences on Docker hub. With the recent announcement to deprecate the Microsoft container hub images and distribution on Docker hub, I suggest to update the readme references to remove link to the post which describes discovery experience on Docker hub as it is no longer relevant.

Can't list tags for various repos on MCR

The repos listed below are included in https://mcr.microsoft.com/v2/_catalog, but the corresponding tags page is missing (error: BlobNotFound).

The tags page for (eg) mssql/tools is referenced from: https://hub.docker.com/_/microsoft-mssql-tools so I expect it should exist.

Repo	Tags List URL
aks/hcp/nginx	https://mcr.microsoft.com/v2/aks/hcp/nginx/tags/list
cosmosdb/winsrv2019lite/azure-cosmos-emulator	https://mcr.microsoft.com/v2/cosmosdb/winsrv2019lite/azure-cosmos-emulator/tags/list
azuredefender/stable/pod-collector	https://mcr.microsoft.com/v2/azuredefender/stable/pod-collector/tags/list
azuredefender/stage/pod-collector	https://mcr.microsoft.com/v2/azuredefender/stage/pod-collector/tags/list
azuredevspaces/azds-build-service	https://mcr.microsoft.com/v2/azuredevspaces/azds-build-service/tags/list
azuredevspaces/azds-image-prepull	https://mcr.microsoft.com/v2/azuredevspaces/azds-image-prepull/tags/list
azuredevspaces/azds-proxy	https://mcr.microsoft.com/v2/azuredevspaces/azds-proxy/tags/list
azuredevspaces/azds-proxy-init	https://mcr.microsoft.com/v2/azuredevspaces/azds-proxy-init/tags/list
azuredevspaces/azds-webhook-service	https://mcr.microsoft.com/v2/azuredevspaces/azds-webhook-service/tags/list
azuredevspaces/devhostagent	https://mcr.microsoft.com/v2/azuredevspaces/devhostagent/tags/list
azuredevspaces/azds-vsdbg	https://mcr.microsoft.com/v2/azuredevspaces/azds-vsdbg/tags/list
azuredevspaces/javadebug	https://mcr.microsoft.com/v2/azuredevspaces/javadebug/tags/list
azure-functions/meshtest	https://mcr.microsoft.com/v2/azure-functions/meshtest/tags/list
azureml/o16n-base/python	https://mcr.microsoft.com/v2/azureml/o16n-base/python/tags/list
azureml/r-base	https://mcr.microsoft.com/v2/azureml/r-base/tags/list
azureml/cmk8s/aml-addon-gateway	https://mcr.microsoft.com/v2/azureml/cmk8s/aml-addon-gateway/tags/list
azureml/cmk8s/job-cleaner	https://mcr.microsoft.com/v2/azureml/cmk8s/job-cleaner/tags/list
azureml-studio/base-gpu	https://mcr.microsoft.com/v2/azureml-studio/base-gpu/tags/list
azuremonitor/containerinsights/citest	https://mcr.microsoft.com/v2/azuremonitor/containerinsights/citest/tags/list
azuremonitor/containerinsights/prod4/preview/azuremonitor-containers	https://mcr.microsoft.com/v2/azuremonitor/containerinsights/prod4/preview/azuremonitor-containers/tags/list
azuremonitor/containerinsights/prod5/preview/azuremonitor-containers	https://mcr.microsoft.com/v2/azuremonitor/containerinsights/prod5/preview/azuremonitor-containers/tags/list
azuremonitor/containerinsights/prod6/preview/azuremonitor-containers	https://mcr.microsoft.com/v2/azuremonitor/containerinsights/prod6/preview/azuremonitor-containers/tags/list
azuremonitor/containerinsights/prod6/stable/azuremonitor-containers	https://mcr.microsoft.com/v2/azuremonitor/containerinsights/prod6/stable/azuremonitor-containers/tags/list
azure-stream-analytics/simulated-sensor	https://mcr.microsoft.com/v2/azure-stream-analytics/simulated-sensor/tags/list
bioconductor/msgen_top30	https://mcr.microsoft.com/v2/bioconductor/msgen_top30/tags/list
azure-cognitive-services/form-recognizer/layout	https://mcr.microsoft.com/v2/azure-cognitive-services/form-recognizer/layout/tags/list
azure-cognitive-services/vision/custom-image-analysis	https://mcr.microsoft.com/v2/azure-cognitive-services/vision/custom-image-analysis/tags/list
csedevops/lucidity/eshoponweb	https://mcr.microsoft.com/v2/csedevops/lucidity/eshoponweb/tags/list
iot/industrial-iot-users-service	https://mcr.microsoft.com/v2/iot/industrial-iot-users-service/tags/list
iot/industrial-iot-auth-service	https://mcr.microsoft.com/v2/iot/industrial-iot-auth-service/tags/list
k8s/genesys/manager	https://mcr.microsoft.com/v2/k8s/genesys/manager/tags/list
k8se/containerapp-controller-api	https://mcr.microsoft.com/v2/k8se/containerapp-controller-api/tags/list
mir/mir-base-image-win1809	https://mcr.microsoft.com/v2/mir/mir-base-image-win1809/tags/list
mir/mir-tokenrefresh-win1809	https://mcr.microsoft.com/v2/mir/mir-tokenrefresh-win1809/tags/list
robotics-ros/melodic-desktop_full	https://mcr.microsoft.com/v2/robotics-ros/melodic-desktop_full/tags/list
mssql/tools	https://mcr.microsoft.com/v2/mssql/tools/tags/list
mssql/rhel/ha	https://mcr.microsoft.com/v2/mssql/rhel/ha/tags/list
arcdata/mssql-security-support	https://mcr.microsoft.com/v2/arcdata/mssql-security-support/tags/list
terraform-on-azure/shell	https://mcr.microsoft.com/v2/terraform-on-azure/shell/tags/list
vscode/devcontainers/powershell	https://mcr.microsoft.com/v2/vscode/devcontainers/powershell/tags/list
vscode/devcontainers/dart	https://mcr.microsoft.com/v2/vscode/devcontainers/dart/tags/list
vscode/devcontainers/swift	https://mcr.microsoft.com/v2/vscode/devcontainers/swift/tags/list

docker debian net core image bug

FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
RUN apt-get -qq update && apt-get -qqy --no-install-recommends install wget gnupg \
    git \
    unzip
RUN curl -sL https://deb.nodesource.com/setup_6.x |  bash -
RUN apt-get install -y nodejs

This is the docker file. I want to download nodejs to the container because I am building a spa app.

This is the error I get

=> ERROR [2/4] RUN apt-get -qq update && apt-get -qqy --no-install-recommends install wget gnupg     git     unzip                                                                                  1.0s
------
 > [2/4] RUN apt-get -qq update && apt-get -qqy --no-install-recommends install wget gnupg     git     unzip:
#5 0.932 E: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/main/binary-amd64/by-hash/SHA256/b7ca340d6ca71e1f8e2ca05da724786dbd3dbab5cef724b237280668073608e1  File has unexpected size (13229 != 258108). Mirror sync in progress? [IP: 199.232.110.132 80]
#5 0.932    Hashes of expected file:
#5 0.932     - Filesize:258108 [weak]
#5 0.932     - SHA256:b7ca340d6ca71e1f8e2ca05da724786dbd3dbab5cef724b237280668073608e1
#5 0.932     - MD5Sum:ec6c3fc6556b5b52078a8304148e403b [weak]
#5 0.932    Release file created at: Thu, 31 Dec 2020 15:31:33 +0000
#5 0.932 E: Failed to fetch http://deb.debian.org/debian/dists/buster/main/binary-amd64/by-hash/SHA256/c88216232d353afbc95e57a5ad04fc515335fb75659dbcae6967cd1109b7e4fb  File has unexpected size (13179 != 7907472). Mirror sync in progress? [IP: 199.232.110.132 80]
#5 0.932    Hashes of expected file:
#5 0.932     - Filesize:7907472 [weak]
#5 0.932     - SHA256:c88216232d353afbc95e57a5ad04fc515335fb75659dbcae6967cd1109b7e4fb
#5 0.932     - MD5Sum:6043a440cb8038062bed716e76b3d7e7 [weak]
#5 0.932    Release file created at: Sat, 05 Dec 2020 10:35:57 +0000
#5 0.932 E: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/main/binary-amd64/by-hash/SHA256/55463230b47ea54463b1a8e687f24d60c0c8d4dccd1868ef26713e3fe11f7f20  File has unexpected size (13195 != 7860). Mirror sync in progress? [IP: 199.232.110.132 80]
#5 0.932    Hashes of expected file:
#5 0.932     - Filesize:7860 [weak]
#5 0.932     - SHA256:55463230b47ea54463b1a8e687f24d60c0c8d4dccd1868ef26713e3fe11f7f20
#5 0.932    Release file created at: Fri, 01 Jan 2021 02:07:51 +0000
#5 0.932 E: Some index files failed to download. They have been ignored, or old ones used instead.
------

I have tried looking into this error but have found nothing useful. If someone can suggest a different route to get nodejs on a container built from a dotnet core image that is fine as well. Thank you.

Builds for arm64

As arm machines are becoming more popular (mostly due to the new apple silicon machines), it would be beneficial to start building arm64 images for both these & the new arm64 raspberry pi's.

MCR too slow in Costa Rica

Okay so I've went through a lot of struggle with different ISPs here (had to move to a new home, so that's why) and no matter the ISP, downloading from mcr.microsoft.com is an ordeal.

This is going at around 200Kb/s (and my FTTH is 100/100mbps...):

Or even less, watch the graph below:

Ping just hangs there:

Speedtest shows a different story though (I'm capped at 50mb/s due to my current network devices in-between):

Same for Fast.com:

So, I read somewhere here that the idea of creating mcr.microsoft.com was for it to be the trusted source for docker container images from Microsoft. However, reliability is included in trust, and unfortunately that decision makes MCR very unreliable in this side of the world, therefore I can't just trust MCR. I need something better. A mirror would be a good idea, or fix the central server if you don't want to make mirrors, but these speeds are just ridiculous.

Any ideas are appreciated, this is really hampering my development speed and reliability on my side because all I can do is just sit down and wait until the images finish downloading without any other alternative (like Docker Hub, which works flawlessly).

mcr.microsoft.com/dotnet/core/aspnet:3.1.16-focal-arm32v7 missing gnupg package required to verify repo sigs

root@bananapim3:~# docker run -it mcr.microsoft.com/dotnet/core/aspnet:3.1.10-focal-arm32v7 /bin/bash
Unable to find image 'mcr.microsoft.com/dotnet/core/aspnet:3.1.10-focal-arm32v7' locally
3.1.10-focal-arm32v7: Pulling from dotnet/core/aspnet
a3a20c5d313f: Pull complete
67966bd810ce: Pull complete
c8282ed68976: Pull complete
92b273b769b6: Pull complete
fc3bfea222ac: Pull complete
e03f56c977a3: Pull complete
19d757a28658: Pull complete
Digest: sha256:086a0fe9dbcff5f32d63f237cb05ae30d112126f2b01e3c11aa74fdd11854989
Status: Downloaded newer image for mcr.microsoft.com/dotnet/core/aspnet:3.1.10-focal-arm32v7
root@a0f522368269:/# apt-get update
Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [101 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
At least one invalid signature was encountered.
Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
At least one invalid signature was encountered.
Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease
At least one invalid signature was encountered.
Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease
At least one invalid signature was encountered.
Reading package lists... Done
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

root@a0f522368269:/# apt-key list
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation

This could be worked around by an insecure add of gnupg, but wouldn't it be better to have this in place from the start?

Or am I missing something?

certificate has expired or is not yet valid on mcr.microsoft.com/dotnet/sdk:5.0

Hello,

I got an error when i'm trying to pull mcr.microsoft.com/dotnet/sdk:5.0

What i should do?

Thanks

Benjamin

Extremely slow pull mcr.microsoft.com/dotnet/sdk:5.0 in Moscow (Russia)

I'm experiencing extremely slow image pull in Moscow (Russia)

[build 1/7] FROM mcr.microsoft.com/dotnet/sdk:5.0@sha256:48922a379d1f54390d5b8655933d3a62877c1fd46d44ab39cb4133fb1d230681
sha256:e98a60ea39354b242a6cddc260cf41743d5738890323240e609fb91369cc5c19 17.07MB / 17.07MB 290.2s done
sha256:62b021f1f14578ffb7f9b9860e9bef156bd26bda5dd16c671d8ce850a5b88110 155B / 155B 290.8s done
...
sha256:018bf2f450f77abab99a693b26a25fcbd9f6ea985533a8448817574a1fb3624d 103.28MB / 103.28MB 911.2s done

microsoft / containerregistry Goto Github PK

containerregistry's Introduction

Microsoft Artifact Registry (MAR)

Browsing MAR Content

Additional Guidance for the Use of MAR

Providing Feedback

FAQ

Legal Notices

containerregistry's People

Contributors

Stargazers

Watchers

Forkers

containerregistry's Issues

Steps to reproduce the issue

Expected behavior

Actual behavior

Additional information (e.g. issue happens only occasionally)

Output of docker version

Output of docker info

**> [internal] load metadata for docker.io/microsoft/aspnetcore:latest:

Steps to reproduce the issue

Steps to reproduce the issue

Expected behavior

Actual behavior

Additional information (e.g. issue happens only occasionally)

Recommend Projects

Recommend Topics

Recommend Org

Output of `docker version`

Output of `docker info`