`add_dockerfile_with_renv`: building Dockerfile ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

[yogat3ch]

Hey team ThinkR,
@keatonwilson and I are testing out the new add_dockerfile_with_renv functionality and are finding that it works on one of our machines with no issue.
However, on my machine, after the Dockerfile_base image is built successfully. Building the image from the Dockerfile that starts with the base image results in the following error

#3 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
------
 > [internal] load metadata for docker.io/library/dmdu_base:latest:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

You can see in the above error where the base build successfully completes, and then the Dockerfile build fails to retrieve the base image at the start.

We're logged into the same docker account via docker desktop and both running MacOSX Monterey 12.5, though his Mac is on the Intel architecture while mine is on the arm64 architecture.
We've tried using docker login and running the build command in sudo sudo docker build ... both of which make no difference.

Any ideas on what's happening here?

[VincentGuyader]

hi,
(sorry for the looong delay)

do you have any reproductible example ?

Regards

[yogat3ch]

Hi @VincentGuyader,
Thanks for chiming in here and sorry for the delay. We've moved to automated Docker builds on AWS infrastructure. We're hoping to start from a cached image, similar to what is described in this issue. When we get there, if we encounter this same issue, I'll follow up. Otherwise if we're able to do it without issue, I'll close the issue.