ERROR: failed to solve: lease "[GUID]": not found

Image Builds
1

I have an odd one - perhaps somebody can help…

I am unable to build a rocky 10 image on one of my servers with even the simplest Dockerfile:

FROM rockylinux/rockylinux:10
ENV HTTP_PROXY="http://1.2.3.4:8080"
ENV HTTPS_PROXY="http://1.2.3.4:8080"
CMD ["/bin/cat","/etc/os-release"]

The error I receive is:

ERROR: failed to solve: lease "fec44sx3nk42ttblsdwwq9mgc": not found

If I change it to:

FROM rockylinux/rockylinux:9

… it builds fine. It also builds fine on another server. What could be the problem?

Thanks.

2

This kind of error message is not familiar to me, but we usually need the following information to understand the issue:

  1. What platform are you using? Windows, Linux or macOS? Which version of the operating systems? In case of Linux, which distribution?

  2. How did you install Docker? Sharing the platform almost answers it, but only almost. Direct links to the followed guide can be useful.

  3. On debian based Linux, the following commands can give us some idea and recognize incorrectly installed Docker:

    docker info
docker version

    Review the output before sharing and remove confidential data if any appears (public IP for example)

    dpkg -l 'docker*' | grep '^ii'
snap list docker
3

Sorry, should have made that clear.

  1. RedHat 9.5
  2. The usual “dnf -y install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin”. There is a proxy too.
  3. docker info
    Client: Docker Engine - Community
Version:    27.5.1
Context:    default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version:  v0.20.0
Path:     /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version:  v2.32.4
Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 14
Running: 0
Paused: 0
Stopped: 14
Images: 21
Server Version: 27.5.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.2.4-0-g6c52b3f
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 5.14.0-503.23.2.el9_5.x86_64
Operating System: Red Hat Enterprise Linux 9.5 (Plow)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.572GiB
Name: \[hostname\]
ID: cf261516-5240-46d8-bbea-a9f75b3037cb
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http://\[IP:port\]/
HTTPS Proxy: http://\[IP:port\]/
Username: \[username\]
Experimental: false
    docker version
    Client: Docker Engine - Community
Version:           27.5.1
API version:       1.47
Go version:        go1.22.11
Git commit:        9f9e405
Built:             Wed Jan 22 13:42:45 2025
OS/Arch:           linux/amd64
Context:           default

Server: Docker Engine - Community
Engine:
Version:          27.5.1
API version:      1.47 (minimum version 1.24)
Go version:       go1.22.11
Git commit:       4c9b3b0
Built:            Wed Jan 22 13:41:04 2025
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.7.25
GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc:
Version:          1.2.4
GitCommit:        v1.2.4-0-g6c52b3f
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
4

Thanks for the details. I originally removed the reference to our formatting guide from the question template I shared in my previous post, because you properly formatted your first post. Please, keep that good habit. I added a little formatting to your last reply as well so it is more obvious what output belongs to what command.

I found an old issue in the Moby repository (The base of Docker CE)

They did not exactly figure out what happened, but the user reinstalled everything and that fixed the issue. You have the latest v27, which is still referenced in the list of release pages, but there was no v27 release since v28 was released. If you can’t or don’t want to update, I recommend opening a new ticket in the same github repository I lnked above.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.