"sleep(1)", but with Go duration parsing OR explicit time to sleep until and a progress bar
Update docker-master
Would a command just to OCIfy a docker image be helpful? That's something we've found a need for in the past and then punted on.
I'm 99% sure there's a PR to do this somewhere.
Looks like that's #1293 (also relevant is #1245)
Update github-pages to 228
Update microsoft-edge/beta to 110.0.1587.35-1
Merge pull request #367 from tianon/update-versions
Update versions
Update docker-master
Changes:
Changes:
Changes:
Changes:
That error sounds like it might be related to https://github.com/moby/buildkit/issues/3576
When docker:dind-rootless
starts and a volume is configured on /certs/ca
, the daemon cannot generate TLS certificates and falls back to non-TLS with errors like:
dockerd | genrsa: Can't open "/certs/ca/key.pem" for writing, Permission denied
dockerd | Could not open file or uri for loading private key from /certs/ca/key.pem
dockerd | 481B2FF9CC7F0000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered scheme:crypto/store/store_register.c:237:scheme=file
dockerd | 481B2FF9CC7F0000:error:80000002:system library:file_open:No such file or directory:providers/implementations/storemgmt/file_store.c:267:calling stat(/certs/ca/key.pem)
The daemon still starts but without TLS.
Minimal reproducible example with Compose:
version: "3.9"
services:
dockerd:
image: docker:23.0.0-dind-rootless
container_name: dockerd
privileged: true
volumes:
- docker_certs_client:/certs/client
- docker_certs_ca:/certs/ca
volumes:
docker_certs_client:
docker_certs_ca:
A workaround is to mount /certs
instead, but it's less secure when sharing volume with other containers are CA data is also available to "client" containers.
prevent tls being disabled if _tls_generate_certs fails
Merge pull request #398 from infosiftr/complex-expressions
prevent tls being disabled if _tls_generate_certs fails
If TLS is requested (via DOCKER_TLS_CERTDIR
) and the directory is not writable, then it should not silently disable TLS.
Fixes https://github.com/docker-library/docker/issues/397
ruby:3.2.0-alpine3.17 needs to be rebuilt to remove CVE-2023-24056 with pkgconf
pkgconf CVE-2023-24056 CRITICAL vulnerable version: 1.9.3-r0 fixed in 1.9.4-r0
alpine:3.17 has fixed this. Rebuild should resolve.
Duplicate of #402
The most notable change here besides the loss of riscv64
on unstable is https://github.com/debuerreotype/debuerreotype/pull/142, or that we no longer ship /etc/apt/sources.list
for debian:bookworm
(next stable) but rather prefer the new deb822-style sources file in /etc/apt/sources.list.d/debian.sources
as debian:unstable
has been shipping for a while now (https://lists.debian.org/debian-devel-announce/2023/02/msg00000.html).
emqx 5.0.16
Merge pull request #14014 from id/emqx-5.0.16
emqx 5.0.16
retire gazebo 9 images
Signed-off-by: Mikael Arguedas mikael.arguedas@gmail.com
Merge pull request #14013 from ros-infrastructure/gazebo9_eol
[gazebo] retire gazebo 9 images
Gazebo 9 has reached EOL: https://community.gazebosim.org/t/gazebo-classic-9-officially-end-of-life/1773 This PR retires the corresponding docker images
Also adresses https://github.com/docker-library/official-images/pull/13950#issuecomment-1412515624
Nice, glad you got it solved - so this can be closed?
I guess https://github.com/memcached/memcached/wiki/ConfiguringServer#inspecting-running-configuration is probably the best way to check if your settings are actually working, but we don't add anything extra above what memcached itself does in this regard.
Does memcached itself support those environment variables? (We don't add any extra behavior here for handling environment variables like in some other images.)