Problem running the Distribution Image Dockerfile example on the README.md page.

[mikebrady]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem

Description

When I run the sample Dockerfile:

FROM ubuntu
COPY --from=crazymax/alpine-s6-dist:3.20 / /
RUN apt-get update && apt-get install -y nginx
RUN echo "daemon off;" >> /etc/nginx/nginx.conf
CMD ["/usr/sbin/nginx"]
ENTRYPOINT ["/init"]

I get the following error:

#8 [stage-0 3/5] COPY --from=crazymax/alpine-s6-dist:3.20 / /
#8 ERROR: cannot copy to non-directory: /var/lib/docker/overlay2/9w1lfin18veqo3rhop8qnxbca/merged/lib
------
 > [stage-0 3/5] COPY --from=crazymax/alpine-s6-dist:3.20 / /:
------
Dockerfile:3
--------------------
   1 |     FROM ubuntu
   2 |     RUN apt-get update
   3 | >>> COPY --from=crazymax/alpine-s6-dist:3.20 / / 
   4 |     RUN apt-get update && apt-get install -y nginx
   5 |     RUN echo "daemon off;" >> /etc/nginx/nginx.conf
--------------------
ERROR: failed to solve: cannot copy to non-directory: /var/lib/docker/overlay2/9w1lfin18veqo3rhop8qnxbca/merged/lib

Expected behaviour

Build should complete...

Actual behaviour

I get the following error:

#8 [stage-0 3/5] COPY --from=crazymax/alpine-s6-dist:3.20 / /
#8 ERROR: cannot copy to non-directory: /var/lib/docker/overlay2/9w1lfin18veqo3rhop8qnxbca/merged/lib
------
 > [stage-0 3/5] COPY --from=crazymax/alpine-s6-dist:3.20 / /:
------
Dockerfile:3
--------------------
   1 |     FROM ubuntu
   2 |     RUN apt-get update
   3 | >>> COPY --from=crazymax/alpine-s6-dist:3.20 / / 
   4 |     RUN apt-get update && apt-get install -y nginx
   5 |     RUN echo "daemon off;" >> /etc/nginx/nginx.conf
--------------------
ERROR: failed to solve: cannot copy to non-directory: /var/lib/docker/overlay2/9w1lfin18veqo3rhop8qnxbca/merged/lib

Steps to reproduce

Run the sample script on a Raspberry Pi 5.

Docker info

pi@RaspberryPi5B:~/s6exp $ docker info
Client: Docker Engine - Community
 Version:    27.4.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 1
 Server Version: 27.4.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 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: 88bf19b2105c8b17560993bee28a01ddc2f97182
 runc version: v1.2.2-0-g7cb3632
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.6.62+rpt-rpi-2712
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 7.864GiB
 Name: RaspberryPi5B
 ID: db90443e-1b19-40a5-99e8-c2b359a86d04
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

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

Docker Compose config

pi@RaspberryPi5B:~/s6exp $ docker compose config
no configuration file provided: not found

Logs

N/A

Additional info

Thanks for all your work, and apologies if this has a really obvious solution!

[crazy-max]

--from=crazymax/alpine-s6-dist:3.20

tag is not correct, see https://github.com/crazy-max/docker-alpine-s6/?tab=readme-ov-file#supported-tags

[crazy-max]

Oh nevermind, that seems to be related to docker host configuration, let me check