Hi,
I enjoy the functionality of the xgo Docker images. But the sheer size and number of layers presents some difficulty. I use buildx (technically tug) to build sets of cross-architecture images. Each time I troubleshoot the Docker image build process, it often ignores caches and has to redownload the layers all over again. Some of the layers are multiple GB.
I recognize that cross-compilation work of native C/C++ code often involves a hefty development environment. Open to ideas for how we can trim away some disk usage, without sacrificing support for the various platforms.
Hi,
I enjoy the functionality of the xgo Docker images. But the sheer size and number of layers presents some difficulty. I use buildx (technically tug) to build sets of cross-architecture images. Each time I troubleshoot the Docker image build process, it often ignores caches and has to redownload the layers all over again. Some of the layers are multiple GB.
I recognize that cross-compilation work of native C/C++ code often involves a hefty development environment. Open to ideas for how we can trim away some disk usage, without sacrificing support for the various platforms.