3 ms·
I think a lot of the complexity with creating containers these days is the pushing to a registry part. Last time I looked at doing it with curl, it was a lot m
by candiddevmike 4y ago
I think a lot of the complexity with creating containers these days is the pushing to a registry part. Last time I looked at doing it with curl, it was a lot more involved than the tar dance. The article glosses over this, I think.
Also not sure how you build multi-arch containers.
- dijit 4y agoI've been trying for a while to build multi-arch containers in CI. I was trying to do it using `manifest-tool`[0] which seems like is mostly deprecated in favour of `docker manifest` If I use manifest-tool on my local machine against GCR (google container registry) it seems to work, but if I use it in CI with `docker-credentials-gcr` it does not work at all.. go figure. What you would generally do is create a docker image for each of your variants (arm64, amd64, windows, linux, macos(who does this?)) then merge them: manifest-tool push from-args \ --platforms linux/amd64,linux/arm/v5,linux/arm/v7 \ --template foo/bar-ARCHVARIANT:v1 \ --target foo/bar:v1 [0]: https://github.com/estesp/manifest-tool https://github.com/estesp/manifest-tool
- tacker2000 4y agoYou can use ansible to push self built images to amazon’s ECR (elastic container registry). Works pretty well for my deployments.
- nyolfen 4y ago> Also not sure how you build multi-arch containers. not sure whether this is the preferred method or what, but i use `docker buildx` -- eg: docker buildx build --tag myimage:mytag --platform linux/amd64,linux/arm64 . this builds the image inside a qemu vm for the non-native architecture
- candiddevmike 4y agoYes, that's what I use currently. I meant without docker/just with tar and friends.