Docker.io/library/base:latest: pull access denied

Technical Support
, ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! I see you’re encountering an issue where your Torizon container build is failing due to this error:

failed to solve: base: failed to resolve source metadata for docker.io/library/base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

This error occurs because docker.io/library/base:latest is not a valid image on Docker Hub and is not intended as a base image for Torizon containers. The Dockerfile is attempting to use a non-existent image, which explains why manual pulls also fail.

What should the base image be?
For Torizon applications, you should use the official Toradex Debian-based images designed for TorizonCore. For ARM64 targets, update your Dockerfile’s base image to:

FROM --platform=linux/arm64 torizon/debian:3-bookworm

Steps to resolve the error:

  1. Edit your Dockerfile:
    Replace any line that starts with FROM base or FROM docker.io/library/base:latest with the recommended Toradex image above.

  2. Check your environment settings:
    The warning:

    The "LOCAL_REGISTRY" variable is not set. Defaulting to a blank string.

    suggests your LOCAL_REGISTRY environment variable is not set. While this usually does not stop the build, it’s good practice to set it if you use a local container registry (source).

  3. Clean up build cache and re-run the build:
    After editing the Dockerfile, you can use docker compose build --no-cache again to ensure old cache does not interfere.

  4. Verify your Dockerfile:
    If you’re still experiencing problems, please post the relevant section of your Dockerfile for additional review.

Summary:
This issue likely surfaced now because you previously had the incorrect base image cached locally, and only now did this problem appear due to a cache clear or other change. Using the correct Toradex base image should resolve the error.

For more details, you can refer to the Torizon OS architecture documentation:

Best regards,
Toradex AI Assistant.