amazon-ecr-credential-helper VS lima

Install the AWS ECR Docker Credential Helper in your runner

Instead of doing that you can download the official ecr-login credential helper tool (a binary built with Go) and configure Docker to use this helper tool every time you interact with the registry. So to you, the user, the authentication is happening in the background and you can push and pull without doing anything.

IAM instance profile that allows ECR actions. Then set up ecr credential helper so docker pull will just work.

You can use the ECR credential helper which rotates the credentials for you: https://github.com/awslabs/amazon-ecr-credential-helper

AWS ECR credential helper though..

Based on what I am seeing here, I would check for a ~/.docker/config.json file or an /etc/docker/config.json to see if anything could be misconfigured.

Use https://github.com/awslabs/amazon-ecr-credential-helper posted in another reply https://www.reddit.com/r/aws/comments/p5e9td/ecr_in_larger_organisations_looking_for_opinions/h95bv9b/

You can run a virtual machine (e.g. lima) from inside a nix-shell, exactly as you would do with a regular shell.

for others similarly curious, here's an example of the thing: https://github.com/noop-inc/template-java-spring-boot/blob/m...

they seem to be using the excellent lima <https://github.com/lima-vm/lima#readme> for booting on macOS; I run colima for its containerd and k8s support but strongly recommend both projects $(brew install lima colima)

Lima is what I use as well. It's quick and easy to just fire up a VM with default settings, but also very easy to configure with different file sharing options, port forwarding, different linux distributions, etc. (their examples are also pretty good IMO [1]).

In particular I use it to run an amd64 VM, which I need to run a stubborn service for work that doesn't run on arm CPUs.

[1] https://github.com/lima-vm/lima/tree/master/examples

Lima (1) is a project that packages Linux distros for MacOS and executes them via qemu in the backend. Maybe you could solve your problem by launching one of their vms and inspecting the command line it generates. You might find an option you were missing.

(1) https://github.com/lima-vm/lima

If you wish to delve into all the configuration possibilities for Lima VM, you can visit this resource.

I'd say Lima and Colima should be enough for most use cases:

https://lima-vm.io/

https://github.com/abiosoft/colima

Github: https://github.com/lima-vm/lima

Lima wraps QEMU in a simple CLI, with neat features for container users, such as filesystem sharing and automatic localhost port forwarding, as well as DNS and proxy propagation for enterprise networks. Rancher Desktop wraps Lima with k3s integration and GUI.

Talks: https://github.com/lima-vm/lima/blob/master/docs/talks.md