{"id":57,"date":"2022-03-10T17:22:50","date_gmt":"2022-03-10T08:22:50","guid":{"rendered":"https:\/\/shirakawa.weblike.jp\/blog-page\/?p=57"},"modified":"2025-10-15T18:22:46","modified_gmt":"2025-10-15T09:22:46","slug":"docker%e3%83%90%e3%82%a4%e3%83%8a%e3%83%aa%e3%82%92install%e3%81%97%e3%81%a6%e4%bd%bf%e3%81%a3%e3%81%a6%e3%81%bf%e3%82%8b","status":"publish","type":"post","link":"https:\/\/shirakawa.weblike.jp\/blog-page\/2022\/03\/10\/docker%e3%83%90%e3%82%a4%e3%83%8a%e3%83%aa%e3%82%92install%e3%81%97%e3%81%a6%e4%bd%bf%e3%81%a3%e3%81%a6%e3%81%bf%e3%82%8b\/","title":{"rendered":"Docker(\u30d0\u30a4\u30ca\u30ea)\u3092install\u3057\u305f"},"content":{"rendered":"

static\u30d0\u30a4\u30ca\u30ea\u3092\u5165\u308c\u308b\u3002
\nhttps:\/\/docs.docker.com\/engine\/install\/binaries\/<\/a>
\nInstall daemon and client binaries on Linux<\/p>\n

Prerequisites
\nBefore attempting to install Docker from binaries, be sure your host machine meets the prerequisites:
\n\u30fbA 64-bit installation
\n(OK)
\n\u30fbVersion 3.10 or higher of the Linux kernel. The latest version of the kernel available for your platform is recommended.
\n(OK)
\n\u30fbiptables version 1.4 or higher
\n$ sudo installpkg n\/iptables-1.8.7-x86_64-3.txz
\n$ sudo installpkg l\/libpcap-1.10.1-x86_64-1.txz (\u4e0d\u8db3lib)
\n\u30fbgit version 1.7 or higher
\n$ sudo installpkg d\/git-2.35.1-x86_64-1.txz
\n\u30fbA ps executable, usually provided by procps or a similar package.
\n(OK)
\n\u30fbXZ Utils 4.9 or higher
\n(OK)
\n\u30fbA properly mounted cgroupfs hierarchy; a single, all-encompassing cgroup mount point is not sufficient. See Github issues #2683, #3485, #4568).
\n(OK)<\/p>\n

Secure your environment as much as possible
\nOS considerations
\nEnable SELinux or AppArmor if possible.
\nIt is recommended to use AppArmor or SELinux if your Linux distribution supports either of the two. This helps improve security and blocks certain types of exploits. Review the documentation for your Linux distribution for instructions for enabling and configuring AppArmor or SELinux.
\n(\u591a\u5206\u3069\u3061\u3089\u3082\u4f7f\u3063\u3066\u306a\u3044\u304b\u3089\u7121\u554f\u984c?)<\/p>\n

Docker daemon considerations
\nEnable seccomp security profiles if possible. See Enabling seccomp for Docker.
\n$ zcat \/proc\/config.gz | grep CONFIG_SECCOMP
\nCONFIG_SECCOMP=y
\nCONFIG_SECCOMP_FILTER=y
\n# CONFIG_SECCOMP_CACHE_DEBUG is not set
\n(OK)
\nEnable user namespaces if possible. See the Daemon user namespace options.
\n$ zcat \/proc\/config.gz | grep NAME
\nCONFIG_NAMESPACES=y
\n(OK?)
\nuser namespaces \u3068\u306f\u3001\u3067\u30b0\u30b0\u3063\u305f\uff1a
\nhttps:\/\/gihyo.jp\/admin\/serial\/01\/linux_containers\/0016<\/a>
\n(unshare\u30b3\u30de\u30f3\u30c9(util-linux)\u304c\u4f7f\u3048\u308b\u3063\u3066\u3053\u3068\u306fOK\u3060\u308d\u3046)<\/p>\n

Install static binaries
\nDownload the static binary archive. Go to https:\/\/download.docker.com\/linux\/static\/stable\/ , choose your hardware platform, and download the .tgz file relating to the version of Docker Engine you want to install.
\nExtract the archive using the tar utility. The dockerd and docker binaries are extracted.
\n$ tar xzvf docker-20.10.9.tgz
\nOptional: Move the binaries to a directory on your executable path, such as \/usr\/bin\/. If you skip this step, you must provide the path to the executable when you invoke docker or dockerd commands.
\n($ sudo cp docker\/* \/usr\/bin\/ \u7c21\u5358\u306b\u5916\u305b\u308b\u3088\u3046\u306bpkg\u5316\u3059\u308b\u305f\u3081\u3001\u5b9f\u884c\u3057\u306a\u3044)
\n$ sudo mkdir -p package-docker\/usr
\n$ sudo mv docker package-docker\/usr\/bin
\n$ sudo chown -R root:root package-docker\/usr
\n$ cd package-docker
\n$ sudo makepkg ..\/docker-20.10.9-x86_64-1.tgz
\n$ sudo installpkg ..\/docker-20.10.9-x86_64-1.tgz
\nStart the Docker daemon:
\n$ sudo dockerd &
\n$ docker run hello-world
\nError getting v2 registry: Get “https:\/\/registry-1.docker.io\/v2\/”: x509: certificate signed by unknown authority
\nhttps:\/\/stackoverflow.com\/questions\/50619911\/docke…<\/a>
\n\\
\nhttps:\/\/docs.docker.com\/engine\/reference\/commandli…<\/a>
\nRunning a Docker daemon behind an HTTPS_PROXY
\nWhen running inside a LAN that uses an HTTPS proxy, the Docker Hub certificates will be replaced by the proxy\u2019s certificates. These certificates need to be added to your Docker host\u2019s configuration:
\n1.Install the ca-certificates package for your distribution
\n2.Ask your network admin for the proxy\u2019s CA certificate and append them to \/etc\/pki\/tls\/certs\/ca-bundle.crt
\n3.Then start your Docker daemon with HTTPS_PROXY=http:\/\/username:password@proxy:port\/ dockerd. The username: and password@ are optional – and are only needed if your proxy is set up to require authentication.
\nThis will only add the proxy and authentication to the Docker daemon\u2019s requests – your docker builds and running containers will need extra configuration to use the proxy<\/p>\n

$ sudo installpkg n\/ca-certificates-20211216-noarch-1.txz
\n$ sudo installpkg a\/dcron-4.5-x86_64-11.txz (update-ca-certificates\u306frun-parts\u304c\u5fc5\u8981)
\n\u3053\u3053\u3067\u72ec\u81ea(root)CA\u3092\u4f5c\u308b\u306e\u304b?\u3001\u8a3c\u660e\u66f8\u30d5\u30a1\u30a4\u30eb\u4f5c\u3089\u306a\u3044\u304b\u3093\u306e\u304b\u3002\u30e1\u30f3\u30c9\u30af\u30b5\u304f\u306a\u3063\u3066\u304d\u305f\u304c\u3001
\n\u3069\u3046\u305b\u3044\u3065\u308c\u3084\u3089\u306a\u304d\u3083\u306a\u3089\u3093\u3060\u308d\u3046\u3057\u3001\u3084\u308b\u304b\u3041\u3002(\u7d50\u5c40\u306f\u3084\u3089\u305a\u306b\u6e08\u3093\u3060\u3001\u4ee5\u964d\u53c2\u7167)
\n$ sudo update-ca-certificates<\/p>\n

\u3068\u601d\u3063\u305f\u304c\u3001\u3057\u3070\u3089\u304f\u3057\u3066\u3084\u3063\u3066\u307f\u308b\u3068\u4eca\u5ea6\u306f\u3067\u304d\u305f\u3089\u3057\u3044\u3002update-ca-certificates\u3057\u3066\u304b\u3089
\ndockerd\u3092\u8d77\u52d5\u3057\u76f4\u3057\u305f\u304b\u3089\u304b?
\n$ sudo dockerd &
\n[5] 9926
\ndarkstar:~$ INFO[2025-05-25Txx:yy:zz.543477443+09:00] Starting up
\nWARN[2025-05-25Txx:yy:zz.548029884+09:00] could not change group \/var\/run\/docker.sock to docker: group docker not found
\nINFO[2025-05-25Txx:yy:zz.553847081+09:00] libcontainerd: started new containerd process pid=9935
\nINFO[2025-05-25Txx:yy:zz.554750713+09:00] parsed scheme: “unix” module=grpc
\nINFO[2025-05-25Txx:yy:zz.554781622+09:00] scheme “unix” not registered, fallback to default scheme module=grpc
\nINFO[2025-05-25Txx:yy:zz.554812931+09:00] ccResolverWrapper: sending update to cc: {[{unix:\/\/\/var\/run\/docker\/containerd\/containerd.sock 0 }] } module=grpc
\nINFO[2025-05-25Txx:yy:zz.554844709+09:00] ClientConn switching balancer to “pick_first” module=grpc
\nINFO[2025-05-25Txx:yy:zz.689367447+09:00] starting containerd revision=5b46e404f6b9f661a205e28d59c982d3634148f8 version=v1.4.11
\nINFO[2025-05-25Txx:yy:zz.714826691+09:00] loading plugin “io.containerd.content.v1.content”… type=io.containerd.content.v1
\nINFO[2025-05-25Txx:yy:zz.715117400+09:00] loading plugin “io.containerd.snapshotter.v1.aufs”… type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.717565718+09:00] skip loading plugin “io.containerd.snapshotter.v1.aufs”… error=”aufs is not supported (modprobe aufs failed: exit status 1 \\”modprobe: FATAL: Module aufs not found in directory \/lib\/modules\/5.15.19\\\\n\\”): skip plugin” type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.717601981+09:00] loading plugin “io.containerd.snapshotter.v1.btrfs”… type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.717780566+09:00] skip loading plugin “io.containerd.snapshotter.v1.btrfs”… error=”path \/var\/lib\/docker\/containerd\/daemon\/io.containerd.snapshotter.v1.btrfs (ext3) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin” type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.717810871+09:00] loading plugin “io.containerd.snapshotter.v1.devmapper”… type=io.containerd.snapshotter.v1
\nWARN[2025-05-25Txx:yy:zz.718392712+09:00] failed to load plugin io.containerd.snapshotter.v1.devmapper error=”devmapper not configured”
\nINFO[2025-05-25Txx:yy:zz.718416264+09:00] loading plugin “io.containerd.snapshotter.v1.native”… type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.718621600+09:00] loading plugin “io.containerd.snapshotter.v1.overlayfs”… type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.718903426+09:00] loading plugin “io.containerd.snapshotter.v1.zfs”… type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.719100742+09:00] skip loading plugin “io.containerd.snapshotter.v1.zfs”… error=”path \/var\/lib\/docker\/containerd\/daemon\/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin” type=io.containerd.snapshotter.v1
\nINFO[2025-05-25Txx:yy:zz.719126222+09:00] loading plugin “io.containerd.metadata.v1.bolt”… type=io.containerd.metadata.v1
\nWARN[2025-05-25Txx:yy:zz.719158962+09:00] could not use snapshotter devmapper in metadata plugin error=”devmapper not configured”
\nINFO[2025-05-25Txx:yy:zz.719174466+09:00] metadata content store policy set policy=shared
\nINFO[2025-05-25Txx:yy:zz.720702146+09:00] loading plugin “io.containerd.differ.v1.walking”… type=io.containerd.differ.v1
\nINFO[2025-05-25Txx:yy:zz.720753008+09:00] loading plugin “io.containerd.gc.v1.scheduler”… type=io.containerd.gc.v1
\nINFO[2025-05-25Txx:yy:zz.721326067+09:00] loading plugin “io.containerd.service.v1.introspection-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721400543+09:00] loading plugin “io.containerd.service.v1.containers-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721437447+09:00] loading plugin “io.containerd.service.v1.content-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721491970+09:00] loading plugin “io.containerd.service.v1.diff-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721529789+09:00] loading plugin “io.containerd.service.v1.images-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721567686+09:00] loading plugin “io.containerd.service.v1.leases-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721608787+09:00] loading plugin “io.containerd.service.v1.namespaces-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721643480+09:00] loading plugin “io.containerd.service.v1.snapshots-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.721681065+09:00] loading plugin “io.containerd.runtime.v1.linux”… type=io.containerd.runtime.v1
\nINFO[2025-05-25Txx:yy:zz.721841740+09:00] loading plugin “io.containerd.runtime.v2.task”… type=io.containerd.runtime.v2
\nINFO[2025-05-25Txx:yy:zz.721982847+09:00] loading plugin “io.containerd.monitor.v1.cgroups”… type=io.containerd.monitor.v1
\nINFO[2025-05-25Txx:yy:zz.723903133+09:00] loading plugin “io.containerd.service.v1.tasks-service”… type=io.containerd.service.v1
\nINFO[2025-05-25Txx:yy:zz.723970729+09:00] loading plugin “io.containerd.internal.v1.restart”… type=io.containerd.internal.v1
\nINFO[2025-05-25Txx:yy:zz.724600003+09:00] loading plugin “io.containerd.grpc.v1.containers”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724625834+09:00] loading plugin “io.containerd.grpc.v1.content”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724655042+09:00] loading plugin “io.containerd.grpc.v1.diff”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724680312+09:00] loading plugin “io.containerd.grpc.v1.events”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724700156+09:00] loading plugin “io.containerd.grpc.v1.healthcheck”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724719115+09:00] loading plugin “io.containerd.grpc.v1.images”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724737810+09:00] loading plugin “io.containerd.grpc.v1.leases”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724759070+09:00] loading plugin “io.containerd.grpc.v1.namespaces”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.724777408+09:00] loading plugin “io.containerd.internal.v1.opt”… type=io.containerd.internal.v1
\nINFO[2025-05-25Txx:yy:zz.725049703+09:00] loading plugin “io.containerd.grpc.v1.snapshots”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.725076598+09:00] loading plugin “io.containerd.grpc.v1.tasks”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.725096642+09:00] loading plugin “io.containerd.grpc.v1.version”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.725114468+09:00] loading plugin “io.containerd.grpc.v1.introspection”… type=io.containerd.grpc.v1
\nINFO[2025-05-25Txx:yy:zz.725311362+09:00] serving… address=\/var\/run\/docker\/containerd\/containerd-debug.sock
\nINFO[2025-05-25Txx:yy:zz.725369312+09:00] serving… address=\/var\/run\/docker\/containerd\/containerd.sock.ttrpc
\nINFO[2025-05-25Txx:yy:zz.725434351+09:00] serving… address=\/var\/run\/docker\/containerd\/containerd.sock
\nINFO[2025-05-25Txx:yy:zz.725469637+09:00] containerd successfully booted in 0.040271s
\nINFO[2025-05-25Txx:yy:zz.743241931+09:00] parsed scheme: “unix” module=grpc
\nINFO[2025-05-25Txx:yy:zz.743289346+09:00] scheme “unix” not registered, fallback to default scheme module=grpc
\nINFO[2025-05-25Txx:yy:zz.743334299+09:00] ccResolverWrapper: sending update to cc: {[{unix:\/\/\/var\/run\/docker\/containerd\/containerd.sock 0 }] } module=grpc
\nINFO[2025-05-25Txx:yy:zz.743356330+09:00] ClientConn switching balancer to “pick_first” module=grpc
\nINFO[2025-05-25Txx:yy:zz.744515692+09:00] parsed scheme: “unix” module=grpc
\nINFO[2025-05-25Txx:yy:zz.744548766+09:00] scheme “unix” not registered, fallback to default scheme module=grpc
\nINFO[2025-05-25Txx:yy:zz.744580908+09:00] ccResolverWrapper: sending update to cc: {[{unix:\/\/\/var\/run\/docker\/containerd\/containerd.sock 0 }] } module=grpc
\nINFO[2025-05-25Txx:yy:zz.744604324+09:00] ClientConn switching balancer to “pick_first” module=grpc
\nINFO[2025-05-25Txx:yy:zz.766432592+09:00] [graphdriver] using prior storage driver: overlay2
\nWARN[2025-05-25Txx:yy:zz.803766357+09:00] Your kernel does not support cgroup blkio weight
\nWARN[2025-05-25Txx:yy:zz.803792119+09:00] Your kernel does not support cgroup blkio weight_device
\nINFO[2025-05-25Txx:yy:zz.804324604+09:00] Loading containers: start.
\nINFO[2025-05-25Txx:yy:zz.059651622+09:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0\/16. Daemon option –bip can be used to set a preferred IP address
\nINFO[2025-05-25Txx:yy:zz.138552587+09:00] Loading containers: done.
\nINFO[2025-05-25Txx:yy:zz.197337722+09:00] Docker daemon commit=79ea9d3 graphdriver(s)=overlay2 version=20.10.9
\nINFO[2025-05-25Txx:yy:zz.198506658+09:00] Daemon has completed initialization
\nINFO[2025-05-25Txx:yy:zz.223809737+09:00] API listen on \/var\/run\/docker.sock
\n(\u8d77\u52d5\u30ed\u30b0\u306f\u3001\u3060\u3044\u3076\u5f8c\u306b\u306a\u3063\u3066\u304b\u3089\u63a1\u3063\u305f\u30022025.05)
\n$ docker run hello-world<\/p>\n

Hello from Docker!
\nThis message shows that your installation appears to be working correctly.<\/p>\n

To generate this message, Docker took the following steps:
\n 1. The Docker client contacted the Docker daemon.
\n 2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
\n (amd64)
\n 3. The Docker daemon created a new container from that image which runs the
\n executable that produces the output you are currently reading.
\n 4. The Docker daemon streamed that output to the Docker client, which sent it
\n to your terminal.<\/p>\n

To try something more ambitious, you can run an Ubuntu container with:
\n $ docker run -it ubuntu bash<\/p>\n

Share images, automate workflows, and more with a free Docker ID:
\n https:\/\/hub.docker.com\/<\/p>\n

For more examples and ideas, visit:
\n https:\/\/docs.docker.com\/get-started\/<\/p>\n

Slack\u306e\u57fa\u672c\u74b0\u5883\u3092\u30b3\u30f3\u30c6\u30ca\u306e\u30d9\u30fc\u30b9\u306b\u3059\u308b
\nhttps:\/\/shirakawa.weblike.jp\/blog-page\/2022\/03\/11…<\/a><\/p>\n

\/*************************************************************************************\/
\n2025.05
\n$ docker compose up -d
\n\u3092\u5b9f\u884c\u3057\u305f\u3089\u3001docker compose \u304c\u7121\u3044\u3068\u304d\u305f\u3002https:\/\/shirakawa.weblike.jp\/blog-page\/2024\/01\/27…<\/a>
\n\u4e0a\u306edocker-20.10.9\u306b\u306f\u3001docker-compose(V1)\u304c\u5165\u3063\u3066\u304a\u3089\u305a\u3001\u5225\u9014\u5165\u308c\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u304c\u3001docker-20.10
\n\u304b\u3089\u306f\u3001docker\u306b\u5165\u3063\u3066\u3044\u3066V2\u3068\u306a\u3063\u3066\u3044\u308b\u3089\u3057\u3044(DeepSeek)\u3002docker-20.10.10\u3092Inst\u3059\u308b\u4e8b\u306b\u3057\u305f\u3002\u524d\u56de\u3068
\n\u540c\u3058\u304f\u4ee5\u4e0b\u3092\u53c2\u8003\u3002
\nhttps:\/\/docs.docker.com\/engine\/install\/binaries\/<\/a>
\n$ tar xzvf docker-20.10.10.tgz
\n($ sudo cp docker\/* \/usr\/bin\/ \u7c21\u5358\u306b\u5916\u305b\u308b\u3088\u3046\u306bpkg\u5316\u3059\u308b\u305f\u3081\u3001\u5b9f\u884c\u3057\u306a\u3044)
\n$ sudo mkdir -p package-docker\/usr
\n$ sudo mv docker package-docker\/usr\/bin
\n$ sudo chown -R root:root package-docker\/usr
\n$ cd package-docker
\n$ sudo makepkg ..\/docker-20.10.10-x86_64-1.tgz
\n$ sudo removepkg \/var\/log\/docker-20.10.9-x86_64-1
\n$ sudo installpkg ..\/docker-20.10.10-x86_64-1.tgz
\n$ grep -E ‘bin|lib’ \/var\/log\/packages\/docker-20.10.10-x86_64-1 | sed s@^@\/@ | xargs ldd | grep found
\n(\u4f9d\u5b58\u306e\u4e0d\u8db3\u306f\u7121\u304b\u3063\u305f)
\nStart the Docker daemon:
\n$ sudo dockerd &
\n$ docker run hello-world<\/p>\n

Inst\u3057\u305f\u5f8c\u304b\u3089\u3088\u304f\u898b\u305f\u3089\u3001docker-20.10.9\u3082docker-20.10.10\u3082\u540c\u3058docker-20.10\u306a\u306e\u3067\u610f\u5473\u304c\u7121\u304b\u3063\u305f\u3002
\ndocker-compose\u304c\u7121\u3044\u4ef6\u306f\u3001ChatGPT\u306b\u805e\u3044\u3066Inst\u3057\u305f\u3002
\nDocker Compose CLI \u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u624b\u52d5\u3067\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002
\n$ mkdir -p ~\/.docker\/cli-plugins\/
\n$ curl -SL https:\/\/github.com\/docker\/compose\/releases\/download\/v2.23.3\/docker-compose-linux-x86_64 -o ~\/.docker\/cli-plugins\/docker-compose
\n$ chmod +x ~\/.docker\/cli-plugins\/docker-compose<\/p>\n

\/*************************************************************************************\/<\/p>\n

\n
\n\u53c2\u8003\u60c5\u5831\uff1a
\nCA\uff08Certificate Authority\uff09\uff1a\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u7528\u8a9e\u4e8b\u5178 – \uff20IT
\nhttps:\/\/atmarkit.itmedia.co.jp\/ait\/articles\/0401\/0…<\/a>
\nUbuntu \u3067\u306f ca-certificates \u30d1\u30c3\u30b1\u30fc\u30b8\u3067 CA \u8a3c\u660e\u66f8\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3067\u304d\u308b\u305e
\nhttps:\/\/vividcode.hatenablog.com\/entry\/linux\/ubunt…<\/a>
\nbuster \u306e ca-certificates \u30d1\u30c3\u30b1\u30fc\u30b8\u306b\u95a2\u3059\u308b\u8a73\u7d30 – Debian
\nhttps:\/\/packages.debian.org\/ja\/buster\/ca-certifica…<\/a>
\nMozilla \u30d6\u30e9\u30a6\u30b6\u306b\u540c\u68b1\u306e\u8a3c\u660e\u66f8\u306e\u8a3c\u660e\u6a5f\u95a2\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002SSL \u30d9\u30fc\u30b9\u306e \u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u304c SSL \u63a5\u7d9a\u6642\u306e\u8a8d\u8a3c\u3067\u63a5\u7d9a\u5148\u3092\u78ba\u8a8d\u3059\u308b\u306e\u306b\u4f7f\u308f\u308c\u307e\u3059\u3002 (Slack\u3082\u540c\u3058)
\n\\
\ndocker update-ca-certificates not found\u3001\u3067\u30b0\u30b0\u3063\u305f\uff1a
\n\u72ec\u81ea(root)CA \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u65b9\u6cd5
\nhttps:\/\/qiita.com\/msi\/items\/9cb90271836386dafce3<\/a>
\n\u8a3c\u660e\u66f8\u30d5\u30a1\u30a4\u30eb \u4f5c\u6210\u3001\u3067\u30b0\u30b0\u3063\u305f\uff1a
\n\u81ea\u5df1\u7f72\u540d\u8a3c\u660e\u66f8\u306e\u4f5c\u6210
\nhttps:\/\/qiita.com\/sanyamarseille\/items\/46fc6ff5a0a…<\/a>
\nhttps:\/\/weblabo.oscasierra.net\/openssl-gencert-1\/<\/a><\/p>\n

Install\u307e\u305f\u306f\u5c55\u958b\u6642\u306e\u30e1\u30c3\u30bb\u30fc\u30b8\uff1a
\n\\# ca-certificates (PEM Files of CA Certificates)
\n\\# This package includes PEM files of CA certificates to allow SSL-based
\n\\# applications to check for the authenticity of SSL connections.
\n\\
\n\\# dcron (Dillon’s Cron daemon)
\n\\# The cron daemon runs in the background and executes tasks on behalf of
\n\\# users at the appropriate time. Many timed system tasks are started
\n\\# with cron, such as the nightly indexing with updatedb.
\n\\# dcron was written entirely from scratch by Matthew Dillon.<\/p>\n","protected":false},"excerpt":{"rendered":"

static\u30d0\u30a4\u30ca\u30ea\u3092\u5165\u308c\u308b\u3002 https:\/\/docs.docker.com\/engine\/install\/binaries\/ Install daemon and client binaries on Linux P […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-57","post","type-post","status-publish","format-standard","hentry","category-web-practice"],"_links":{"self":[{"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/posts\/57","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/comments?post=57"}],"version-history":[{"count":26,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/posts\/57\/revisions"}],"predecessor-version":[{"id":1819,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/posts\/57\/revisions\/1819"}],"wp:attachment":[{"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/media?parent=57"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/categories?post=57"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shirakawa.weblike.jp\/blog-page\/wp-json\/wp\/v2\/tags?post=57"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}