dockle stopped working when updating docker to version 25

[tgquan67]

Description

Since I updated docker engine to version 25, I cannot scan images built locally anymore, with or without buildkit. The image is built normally with a dockerfile

docker build . -t a:b --load

And scan with

dockle a:b

This happens on both my local machine with Ubuntu 20.04 and dockle 0.4.11 and my Jenkins system with Ubuntu 20.04 and dockle 0.4.14. I already tried setting DOCKLE_HOST but that did not solve the problem.

What did you expect to happen?
The image is scanned.

What happened instead?

2024-03-05T15:55:55.182+0200    FATAL   unable to initialize a image struct: failed to initialize source: reading manifest b in docker.io/library/a: requested access to the resource is denied

Output of run with -debug:

2024-03-05T15:56:01.945+0200    DEBUG   There is no .dockleignore file
2024-03-05T15:56:01.945+0200    DEBUG   Skipped update confirmation
2024-03-05T15:56:01.945+0200    DEBUG   Start assessments...
2024-03-05T15:56:03.669+0200    FATAL   unable to initialize a image struct:
    github.com/goodwithtech/deckoder/extractor/docker.newDockerExtractor
        /home/runner/go/pkg/mod/github.com/goodwithtech/deckoder@v0.0.3/extractor/docker/docker.go:73
  - failed to initialize source:
    github.com/goodwithtech/deckoder/extractor/image.NewImage
        /home/runner/go/pkg/mod/github.com/goodwithtech/deckoder@v0.0.3/extractor/image/image.go:86
  - reading manifest b in docker.io/library/a: requested access to the resource is denied

Output of dockle -v:

dockle version 0.4.11

Additional details (base image name, container registry info...):
Sample dockerfile used

FROM python:3.8
COPY Pipfile Pipfile.lock .
RUN pip install pipenv && \
    pipenv sync
COPY code.txt .

[lamroger-nava]

I'm having the same issue - did you figure out the problem @tgquan67 ?

edit: I figured it out - the runner / docker was out of space.
I run this before checkout

- name: Delete huge unnecessary tools folder
        run: rm -rf /opt/hostedtoolcache

[tgquan67]

As far as I can see, the problem seems to have been solved with docker 26, not sure what docker did though.