Update docker-compose.yaml

[plever]

Docker hub updated the python 3.11 docker image for some reason... The old one doesn't exist anymore. This one seemed equivalent.

[drewyangdev]

Hi @plever ,
Thanks for posting this! I'm not able to reproduce this issue on my end, I can pull this base image:

(base) drewyang@11:31:11:~$ docker pull mcr.microsoft.com/devcontainers/python:3.11-buster
3.11-buster: Pulling from devcontainers/python
ac8bb7e1a323: Download complete
......
5ef7e07956fd: Download complete
Digest: sha256:2578fb2474b1245a91115030c6b2224aa61c1229426c299793ef321a666d839f
Status: Downloaded newer image for [mcr.microsoft.com/devcontainers/python:3.11-buster](http://mcr.microsoft.com/devcontainers/python:3.11-buster)
[mcr.microsoft.com/devcontainers/python:3.11-buster](http://mcr.microsoft.com/devcontainers/python:3.11-buster)
(base) drewyang@11:31:40:~$ docker images | grep devcontainers
mcr.microsoft.com/devcontainers/python                3.11-buster   2578fb2474b1   6 months ago    2.38GB

and I don't think this related to dockerhub, since this base image wasn't pushed to the dockerhub's docker.io registry, but on the Microsoft's registry mcr.microsoft.com. You can find this image's overview on dockerhub here, but it's actually pointing to here. This image can be found:

[plever]

Drew, I can repro the issue: [1688 ms] Error fetching image details: No manifest found for mcr.microsoft.com/devcontainers/python:3.11-buster. [1688 ms] Start: Run: docker pull mcr.microsoft.com/devcontainers/python:3.11-buster Error response from daemon: no matching manifest for linux/arm64/v8 in the manifest list entries: no match for platform in manifest: not found [2242 ms] [] [2242 ms] Error response from daemon: No such image: mcr.microsoft.com/devcontainers/python:3.11-buster I figured the MS repo was pulling it straight from the base repo but you're right they could be hosting their own version. But the image fetch fails with that buster version. Are you sure you don't have it cached locally? Your log looks like a full fetch though... Just calling it out as the tutorial didn't work for me out of the box without the image update. - Peter Lever

…

On Wed, Jan 29, 2025 at 10:36 AM Drew Yang ***@***.***> wrote: Hi @plever <https://github.com/plever> , Thanks for posting this! I'm not able to reproduce this issue on my end, I can pull this base image: (base) ***@***.***:31:11:~$ docker pull [mcr.microsoft.com/devcontainers/python:3.11-buster](http://mcr.microsoft.com/devcontainers/python:3.11-buster) 3.11-buster <http://mcr.microsoft.com/devcontainers/python:3.11-buster%5D(http://mcr.microsoft.com/devcontainers/python:3.11-buster)3.11-buster>: Pulling from devcontainers/python ac8bb7e1a323: Download complete ...... 5ef7e07956fd: Download complete Digest: sha256:2578fb2474b1245a91115030c6b2224aa61c1229426c299793ef321a666d839f Status: Downloaded newer image for [mcr.microsoft.com/devcontainers/python:3.11-buster](http://mcr.microsoft.com/devcontainers/python:3.11-buster) <http://mcr.microsoft.com/devcontainers/python:3.11-buster%5D(http://mcr.microsoft.com/devcontainers/python:3.11-buster)> [mcr.microsoft.com/devcontainers/python:3.11-buster](http://mcr.microsoft.com/devcontainers/python:3.11-buster) <http://mcr.microsoft.com/devcontainers/python:3.11-buster%5D(http://mcr.microsoft.com/devcontainers/python:3.11-buster)> (base) ***@***.***:31:40:~$ docker images | grep devcontainers [mcr.microsoft.com/devcontainers/python](http://mcr.microsoft.com/devcontainers/python) <http://mcr.microsoft.com/devcontainers/python%5D(http://mcr.microsoft.com/devcontainers/python)> 3.11-buster 2578fb2474b1 6 months ago 2.38GB and I don't think this related to dockerhub, since this base image wasn't pushed to the dockerhub's [docker.io](http://docker.io/) registry, but on the Microsoft's registry [mcr.microsoft.com](http://mcr.microsoft.com/). You can find this image's overview on dockerhub here <https://hub.docker.com/r/microsoft/devcontainers-python>, but it's actually pointing to here <https://mcr.microsoft.com/en-us/artifact/mar/devcontainers/python/tags>. This image can be found: Screenshot.from.2025-01-29.12-30-52.png (view on web) <https://github.com/user-attachments/assets/b45398d4-df73-4ba5-9421-c34d723fc57e> — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGFMIXM3AGJETMX7JTAETT2NENUNAVCNFSM6AAAAABV55ANT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRSGUZTCMJXGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[drewyangdev]

Hi @plever,
Since you encountered an error:

Error response from daemon: no matching manifest for linux/arm64/v8 in the
manifest list entries: no match for platform in manifest: not found

I assume you are using ARM CPU architecture like Mac M1+? Then that's possible the reason, MCR didn't doc the image platform support very clearly, only mentioned x86-64, arm64/aarch64 for bookworm, and bullseye variants. I guess that's why you need to pull a different base image version.

I'll approve your PR, thanks for contributing!