Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker pull buildpack-deps:curl downloads ancient version #166

Open
TimWolla opened this issue Nov 23, 2024 · 3 comments
Open

docker pull buildpack-deps:curl downloads ancient version #166

TimWolla opened this issue Nov 23, 2024 · 3 comments

Comments

@TimWolla
Copy link

On two different systems when pulling buildpack-deps:curl I'm receiving a version from 18 months ago:

My local Ubuntu 20.04 machine:

$ docker images |grep buildpack-deps
buildpack-deps                                                                                         buster          6ea119635dd5   8 months ago    802MB
buildpack-deps                                                                                         buster-curl     69123c546528   8 months ago    147MB
buildpack-deps                                                                                         latest          a847434443a8   10 months ago   930MB
$ docker pull buildpack-deps:curl
curl: Pulling from library/buildpack-deps
b2b31b28ee3c: Already exists 
c3cc7b6f0473: Already exists 
Digest: sha256:41a24bb5f87a336e821481c8495904b7ccab850ddb7d3c7819c2c4e2c7fb7cb9
Status: Downloaded newer image for buildpack-deps:curl
docker.io/library/buildpack-deps:curl
$ docker images |grep buildpack-deps
buildpack-deps                                                                                         buster          6ea119635dd5   8 months ago    802MB
buildpack-deps                                                                                         buster-curl     69123c546528   8 months ago    147MB
buildpack-deps                                                                                         latest          a847434443a8   10 months ago   930MB
buildpack-deps                                                                                         curl            f0afb2b1893c   18 months ago   165MB
$ docker info
Client: Docker Engine - Community
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: *snip*
  Running: *snip*
  Paused: *snip*
  Stopped: *snip*
 Images: *snip*
 Server Version: 27.3.1
 Storage Driver: zfs
  Zpool: scratch
  Zpool Health: ONLINE
  Parent Dataset: *snip*
  Space Used By Parent: *snip*
  Space Available: *snip*
  Parent Quota: no
  Compression: on
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 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: 57f17b0a6295a39009d861b89e3b3b87b005ca27
 runc version: v1.1.14-0-g2c9f560
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
 Kernel Version: 5.4.0-202-generic
 Operating System: Ubuntu 20.04.6 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.735GiB
 Name: *snip*
 ID: *snip*
 Docker Root Dir: *snip*
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

My Debian 11 server:

$ docker images |grep buildpack-deps
buildpack-deps                          scm                408d444d5648   10 months ago   342MB
$ docker pull buildpack-deps:curl
curl: Pulling from library/buildpack-deps
b2b31b28ee3c: Already exists 
c3cc7b6f0473: Already exists 
Digest: sha256:41a24bb5f87a336e821481c8495904b7ccab850ddb7d3c7819c2c4e2c7fb7cb9
Status: Downloaded newer image for buildpack-deps:curl
docker.io/library/buildpack-deps:curl
$ docker images |grep buildpack-deps
buildpack-deps                          scm                408d444d5648   10 months ago   342MB
buildpack-deps                          curl               f0afb2b1893c   18 months ago   165MB
Client: Docker Engine - Community
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: *snip*
  Running: *snip*
  Paused: *snip*
  Stopped: *snip*
 Images: *snip*
 Server Version: 27.3.1
 Storage Driver: zfs
  Zpool: rpool
  Zpool Health: ONLINE
  Parent Dataset: *snip*
  Space Used By Parent: *snip*
  Space Available: *snip*
  Parent Quota: no
  Compression: on
 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: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
 runc version: v1.1.14-0-g2c9f560
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.10.0-33-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.52GiB
 Name: *snip*
 ID: *snip*
 Docker Root Dir: *snip*
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
@LaurentGoderre
Copy link
Member

@TimWolla
Copy link
Author

wow is that terrible UX. Thank you. Should the timestamp perhaps be the timestamp of the base image or the latest git commit, whichever is later, instead? That would at least ensure that the image show up as reasonably recent whenever the base image is rebuilt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants