Is this a known issue? E: Fixed

$ docker pull <http://cr.flyte.org/flyteorg/flytescheduler-release:v1.4.3|cr.flyte.org/flyteorg/flytescheduler-release:v1.4.3>
5e5f900059c8: Download complete
0f96f76f982d: Download complete
88dae1745799: Downloading [>                                                  ]       0B/2.343kB
failed to copy: httpReadSeeker: failed open: failed to do request: Get "<https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:88dae1745799f4078f859b8ada55bc1f1757d10d9c97cdeb62f88cfc827c3a1f?se=2023-03-24T21%3A05%3A00Z&sig=rMhv3oYchaYycF260vI0pdx6pENdYsKpph9eXak%2BMPw%3D&sp=r&spr=https&sr=b&sv=2019-12-12>": x509: certificate is valid for *.<http://githubassets.com|githubassets.com>, <http://githubassets.com|githubassets.com>, not <http://pkg-containers.githubusercontent.com|pkg-containers.githubusercontent.com>

https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/#:~:text=March%2023%2C%202023-,At%20appro[…]0of,their%20Git%20operations%20over%20SSH This snippet will replace the entry in known hosts, & you may need to take a manual action to fix CI nodes if this is happening there

$ ssh-keygen -R <http://github.com|github.com>
$ curl -L <https://api.github.com/meta> | jq -r '.ssh_keys | .[]' | sed -e 's/^/github.com /' >> ~/.ssh/known_hosts

What does docker have to do with SSH?

Ah whoops, I think this may have also led to a cert issue though (we saw a similar flake earlier)

The error is that ssl cert for https://pkg-containers.githubusercontent.com doesn’t have pkg-containers.githubusercontent.com as subject name so download of the layer fails

Ah, nvm then

Looks like it was fixed since I asked