buildx VS aws-graviton-getting-started

This is great! I’ve been waiting a long time for this and it seems like more debug features are in the pipeline too: https://github.com/docker/buildx/issues/1104

Docs: https://docs.docker.com/engine/reference/commandline/buildx_...

Container engine: Docker v23.0.4 | Buildx v0.10.4

ARCH=amd64 # change to 'arm64' for M1 VERSION=v0.10.4 curl -LO https://github.com/docker/buildx/releases/download/${VERSION}/buildx-${VERSION}.darwin-${ARCH} mkdir -p ~/.docker/cli-plugins mv buildx-${VERSION}.darwin-${ARCH} ~/.docker/cli-plugins/docker-buildx chmod +x ~/.docker/cli-plugins/docker-buildx docker buildx version # verify installation

wget -O /tmp/docker/cli-plugins/docker-buildx https://github.com/docker/buildx/releases/tag/v0.10.4/buildx-v0.10.4.linux-amd64

Your particular one looks somewhat like https://github.com/docker/buildx/issues/1595.

Now, we have examples of the actual definitions for a single application’s docker container. Notice that we set the contexts key here which references the dependency targets we just defined. You can basically think of this like the depends_on block if you’ve used Terraform before. The args key let’s us populate the ARG variables in the Dockerfile. This is what is ultimately different between each of the containers. In the future, the buildx team might support using for_each loops like in Terraform but for now each block will have a bit of duplication.

Now as bonus we i will add how to use this techniques to build a multi arch build container. Maybe you have the same application but you need to run it in arm or riscv architecture. For this we can use the buildx plugin from docker https://github.com/docker/buildx.

Third step is docker/setup-buildx-action configures buildx, which is a Docker CLI plugin that provides enhanced build capabilities.

EMR serverless + Athena + Glue works for us. We are evaluating Graviton instance to further optimize stuff. AWS link if you are interested

Now we turn our attention to carbon emissions which are presented in Table 8. In the table, the AMD – CPU only and AMD – T408 server watts/hour are actual measurements on the test system during operation. To estimate the AWS server watts/hour, we reduced the CPU-only AMD number by 60%, which is the savings that Amazon claims that Graviton3 CPUs provide over other CPUs. In all three cases, we multiplied this by the number of servers, then hours, days, and years, to compute the three-year power consumption total.

https://aws.amazon.com/ec2/graviton/ https://cloud.google.com/compute/docs/instances/arm-on-compute

From the relevant product page [0]:

"AWS Graviton3 processors feature always-on memory encryption, dedicated caches for every vCPU, and support for pointer authentication."

Further reading on pointer authentication [1].

[0] https://aws.amazon.com/ec2/graviton/

[1] https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets...

Amazon makes their own Arm CPUs, like the Graviton3: https://aws.amazon.com/ec2/graviton/

Read More about Graviton Processors

According to BlackBerry, both QNX and IVY can run on EC2 instances powered by AWS’ Graviton2 processor. Graviton2 is an internally-developed processor that AWS debuted at re:Invent last year. It promises to provide up to 40% better price performance than comparable chips. "