Hello,
> Nice. The script does not work for me though: > > mikan:~/docker-pike% env DRYRUN=1 ./build-push.sh docker/8.0.1116 > building docker/8.0.1116 > [+] Building 0.0s (0/0) > error: multiple platforms feature is currently not supported for docker > driver. Please switch to a different driver (eg. "docker buildx create --use") > mikan:~/docker-pike% > > Ideas? Looks like your local install is missing the buildx Docker plugin. It’s used by the script to build multi-arch container images. https://docs.docker.com/build/buildx/ Anyhow, the target audience wouldn’t use this behind-of-the-scene script (which should be replaced by a proper CI/CD pipeline), but directly use a container image from a registry : https://hub.docker.com/r/bertrandlupart/pike/tags > Btw, can we add linux/ppc64 to the arch list? I'd like to have riscv > too, but I guess it doesn't have docker yet… Those are using Debian's Pike packages, and any architecture supported should be available (like linux/ppc64le) From your PPC64 machine, you should be able to run the container without building it : $ docker run -it --rm --user pike bertrandlupart/pike:stable-latest pike The point here is that you have to trust containers from my registry. Would we provide containers and other cloud-native Pike solutions, it would be better to have them community-backed. Concerning RISCV, would be a fun addition to this project. For now, seems like Debian an RISCV isn’t a thing, nor Pike Debian packages. Containers look usable on RISCV though : https://carlosedp.medium.com/docker-containers-on-risc-v-architecture-5bc45725624b <https://carlosedp.medium.com/docker-containers-on-risc-v-architecture-5bc45725624b> Bertrand
