@kemingy

If you change the toolchain version, you may need to update the image. I'll create a CI to push the image to GitHub packages so developers can trigger the CI to update the image.

If you change the toolchain version, you may need to update the image. I'll create a CI to push the image to GitHub packages so developers can trigger the CI to update the image.

Why do we need to update the image? Why not add targets when image is used?

If you change the toolchain version, you may need to update the image. I'll create a CI to push the image to GitHub packages so developers can trigger the CI to update the image.

Why do we need to update the image? Why not add targets when image is used?

Adding targets later means you need to do it for every docker image run. Updating the version is not a highly frequent operation.

If you change the toolchain version, you may need to update the image. I'll create a CI to push the image to GitHub packages so developers can trigger the CI to update the image.

Why do we need to update the image? Why not add targets when image is used?

Adding targets later means you need to do it for every docker image run. Updating the version is not a highly frequent operation.

I think adding a target takes less than one second on Github actions and downloading the docker image takes more than one. If we want it to be faster, we should remove docker for first.

Adding targets costs about 17.8s in GitHub CI. Downloading the whole image is about 53s for now, almost the same as downloading from Docker Hub. I thought accessing ghcr should be much faster.

Adding targets costs about 17.8s in GitHub CI.

Their servers must be on the moon or Mars. It takes only 4 seconds even on my machine.