Packer definitions for building minimal Vagrant baseboxes
The Docker CLI
Define and run multi-container applications with Docker
An open and reliable container runtime, by Docker
The Docker toolset to pack, ship, store, and deliver content
An alpine linux environment for building apk packages using docker
Source repo for Docker's Documentation
commit sha 087e9d0c255fff6b032100afb133b20283327e43
Update patches Docker-DCO-1.1-Signed-off-by: Josh Hawn <email@example.com> (github: jlhawn)
commit sha 4e6446f047c298e7fa0e549d818b1f5d1c444c0c
update to alpine 3.9
commit sha f3416af4d2a510988a86719151bbfdb299f8c75f
Merge pull request #7 from ry4nz/alpine-3.9 update to alpine 3.9
commit sha d6828ef92c504437c93b39d3876b7365a36234fe
Bump to Alpine 3.10 Docker-DCO-1.1-Signed-off-by: Josh Hawn <firstname.lastname@example.org> (github: jlhawn)
push time in a month
pull request commentlinuxkit/linuxkit
If I add a
sync and time it separately, I get the following results. It's not so much that the bigger block size is much more efficient, the writes are being cached. Is it safe to use fallocate here instead of dd? I vaguely remember that fallocate might leave "holes" which swap doesn't like.
time dd if=/dev/zero of=output bs=1048576 count=1024 && time sync 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 0.571346 s, 1.9 GB/s real 0m0.572s user 0m0.000s sys 0m0.572s real 0m10.289s user 0m0.000s sys 0m0.000s
comment created time in 2 months
Pull request review commentdocker/docker.github.io
certificate at the OS level. #### Ubuntu ```bash-$ cp certs/domain.crt /usr/local/share/ca-certificates/myregistrydomain.com.crt+$ mkdir -p /etc/docker/certs.d/myregistrydomain.com+$ cp certs/domain.crt /etc/docker/certs.d/myregistrydomain.com
There are two ways to get an engine to trust a registry. The first is adding a root cert to the system trust store, which is what is currently documented in registry/insecure.md.
The second way is to add it to /etc/docker/certs.d/myregistrydomain.com. There is no need to do an "update-ca-certs" type of step. And it might not even be necessary to restart the docker engine (I can't remember). The location is different on windows/mac.
The down side of the second way is that it only affects the engine. You'd also have to tell the CLI about the cert for when it contacts the registry directly (docker trust, docker manifest).
comment created time in 4 months