Currently I am able to use version 3.12 but nothing beyond that. I'm not sure if this is a problem with Alpine or S6. See logs below for the errors. This is on a Pi 3B+. Apologies in advance if there's something obvious I've missed!
Works similar to 3.12.
See logs below.
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.6.3-docker)
Server:
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 17
Server Version: 20.10.9
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
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 logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: 5b46e404f6b9f661a205e28d59c982d3634148f8
runc version: v1.0.2-0-g52b36a2
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.63-v7+
Operating System: Raspbian GNU/Linux 10 (buster)
OSType: linux
Architecture: armv7l
CPUs: 4
Total Memory: 923.2MiB
Name: nova-pi3-01
ID: 5RBG:IODV:BL63:KTOL:ICCN:K3YZ:FUMR:GXIX:ET6J:SSDS:G7BE:MS5S
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory TCP limit support
WARNING: No oom kill disable support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] ~-socklog: executing...
[cont-init.d] ~-socklog: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
s6-log: warning: unable to set monotonic clock and read current time - timestamps may be wrong for a while: Operation not permitted
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-log: warning: unable to set monotonic clock and read current time - timestamps may be wrong for a while: Operation not permitted
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!
s6-supervise socklog: warning: can't happen: timeout while the service is up!
s6-supervise socklog/log: warning: can't happen: timeout while the service is up!