ARM64 Devcontainer

[londospark]

For people who use M1/M2 macs and other ARM64-based devices could we please get an ARM64-native docker image for https://hub.docker.com/r/purtontech/rust-on-nails-devcontainer/?

[ianpurton]

@londospark That's a great idea. If you know how to do it let me know, otherwise I'll do some research.

[londospark]

Thank you - I don't know how to do it off hand but I suspect that someone would need to have access to the original Dockerfile to update the image and add an arm64 version

[hjr3]

We should be able to do this using docker buildx for multi-platform builds.

Example:

$ cd /path/to/rust-on-nails
$ docker buildx build --platform linux/arm64 nails-devcontainer
 ...
 => => writing image sha256:5c9c95cb837f7e6d2c447dbe5a614e8726ba6ee336f49416f840c3431bba27b9
$ docker image inspect --format "{{.Architecture}}" 5c9c95cb837f7e6d2c447dbe5a614e8726ba6ee336f49416f840c3431bba27b9
arm64

See https://docs.docker.com/build/building/multi-platform/ for more information.

I also opened #27 to resolve one issue I ran into when building an arm64 target.

I created a personal image in the meantime: https://hub.docker.com/layers/hjr3/rust-on-nails-devcontainer/db5471a/images/sha256-ed9f94c06d7dffe0865e5d7f44cfe1d0ef870ec0c6fa17498b27406650957de0?context=repo

[ianpurton]

I tried

docker buildx build --platform linux/arm64 dev-env-as-code

And it locked up while trying to build the cornucopia and cargo-chef. I'll ask these guys if they will build binaries as it makes sense that they get built upstream.

Then we'll need to be aware of packages that get downloaded should use these var to get the correct version.

TARGETOS : Target platform operating system. e.g. linux
TARGETARCH: Target platform CPU architecture. e.g. arm64
TARGETVARIANT : Target platform CPU architecture Variant. e.g. v8

[gerwitz]

purtontech/rust-on-nails-devcontainer/ seems to have started including arm64 builds last month, perhaps this issue can be closed?

[anselanza]

Still not 100% correct. I noticed that mold, for instance, is explicitly installed with x86-64 version, e.g.

...
&& curl -OL https://github.com/rui314/mold/releases/download/v$MOLD_VERSION/mold-$MOLD_VERSION-x86_64-linux.tar.gz     && tar -xf mold-$MOLD_VERSION-x86_64-linux.tar.gz     && mv ./mold-$MOLD_VERSION-x86_64-linux/bin/mold /usr/bin/     && mv ./mold-$MOLD_VERSION-x86_64-linux/lib/mold/mold-wrapper.so /usr/bin/     && rm mold-$MOLD_VERSION-x86_64-linux.tar.gz     && rm -rf ./mold-$MOLD_VERSION-x86_64-linux     && chmod +x /usr/bin/mold # buildkit

At least, this is the case in https://hub.docker.com/layers/purtontech/rust-on-nails-devcontainer/1.3.18/images/sha256-53e937d4d78b67f64648fa8a2e049769b9ae7deecb7fdcaf4f4b2e7d82b151ec

[EbaraKoji]

I'm developing with arm64 devcontainer, currently reaching "Building with Components II" section.
Thanks to detailed explanations and highly organized source code, almost everything works fine.
But some x86_64 tools are not executable in built arm64 containers, as expected.

My quick workaround is to replace x86-64 tools with arm64 ones by downloading from sources, although not the optimized build procedure.

# Remove pre-installed x86_64 tailwind-extra and install aarch64 one
RUN sudo rm -f --preserve-root /usr/local/bin/tailwind-extra || true && \
    curl -sL https://github.com/dobicinaitis/tailwind-cli-extra/releases/download/v2.1.31/tailwindcss-extra-linux-arm64 -o /tmp/tailwind-extra && \
    chmod +x /tmp/tailwind-extra && \
    sudo cp /tmp/tailwind-extra /usr/local/bin/ && \
    cd / && rm -rf /tmp/tailwind-extra

As for mold, using arm64 one causes mold-wrapper preload warnings, which is neither the responsibility of this devcontainer nor that of mold.
As I could not find any workaround to disable the annoying warning messages with every compilation, the option might be just to ignore the warning messages or to run cargo watch without mold(my decision).