我有基于xubuntu的linux。
我已经安装了Docker。
但对于我的基础设施,我需要使用
docker-machine
作为一名经理。
问题是
码头装卸机
默认情况下无法看到我的图像
~/.docker
是的。我确实试着设置
MACHINE_STORAGE_PATH
变量设置为
overlay2
存储驱动程序(从这个
answers
)但没有一个能起作用。即使我的Docker有一台正在运行的机器,Docker机器也看不到。
>docker-machine active
No active host found
以及:
>docker info
Containers: 17
Running: 1
Paused: 0
Stopped: 16
Images: 15
Server Version: 18.09.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.16.13-galliumos
Operating System: GalliumOS 3.0
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.791GiB
Name: galliumos
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
如何配置
码头装卸机
看我的Docker图片?
这是我的
/var/lib/docker
以下内容:
/var/lib/docker
âââ builder
â  âââ fscache.db
âââ buildkit
â  âââ cache.db
â  âââ content
â  â  âââ ingest
â  âââ executor
â  âââ metadata.db
â  âââ snapshots.db
âââ containers
â  âââ 077f50df3a86911d1d715f6658e9a0984b16041ebdf7a9497c90a7185c63c17a
â  â  âââ 077f50df3a86911d1d715f6658e9a0984b16041ebdf7a9497c90a7185c63c17a-json.log
â  â  âââ checkpoints
â  â  âââ config.v2.json
â  â  âââ hostconfig.json
â  â  âââ hostname
â  â  âââ hosts
â  â  âââ mounts
â  â  â  âââ shm
â  â  âââ resolv.conf
â  â  âââ resolv.conf.hash
âââ image
â  âââ overlay2
â  âââ distribution
â  â  âââ diffid-by-digest
â  â  â  âââ sha256
â  â  â  âââ fa83472a3562898caaf8d77542181a473a84039376f2ba56254619d9317ba00d
â  â  âââ v2metadata-by-diffid
â  â  âââ sha256
â  â  âââ f75e64f96dbc610a00722afa3826745952db8d1416f6405e7e87c20868b9f542
â  âââ imagedb
â  â  âââ content
â  â  â  âââ sha256
â  â  â  âââ d40668baebcb80ab9c13667d2c62ca359b52bba417415f257313b98fed17d1ef
â  â  âââ metadata
â  â  âââ sha256
â  â  âââ d40668baebcb80ab9c13667d2c62ca359b52bba417415f257313b98fed17d1ef
â  â  âââ parent
â  âââ layerdb
â  â  âââ mounts
â  â  â  âââ fec9fa167f8f6944ca24c1c9fdffe8142392922ad9f8967f095ffdee536e4025
â  â  â  âââ init-id
â  â  â  âââ mount-id
â  â  â  âââ parent
â  â  âââ sha256
â  â  â  âââ eb91e8adb4541f0df58f6d896fee1355e04c0984b3104da1038178b8d6649b6b
â  â  â  âââ cache-id
â  â  â  âââ diff
â  â  â  âââ parent
â  â  â  âââ size
â  â  â  âââ tar-split.json.gz
â  â  âââ tmp
â  âââ repositories.json
âââ network
â  âââ files
â  âââ local-kv.db
âââ overlay2
â  âââ 81957d0e7cac6b00a103bad4da4f12e8103f56f358902aa4c39d9d9b8164917a
â  â  âââ diff
â  â  â  âââ go
â  â  â  âââ bin
â  â  â  âââ all-in-one-linux
â  â  âââ link
â  âââ ffbbee81aeec171e1a70b27f3c3fc7ace6c0ca33dbfdd6d390b406d34b1c8b6d-init
â  â  âââ diff
â  â  â  âââ dev
â  â  â  â  âââ console
â  â  â  â  âââ pts
â  â  â  â  âââ shm
â  â  â  âââ etc
â  â  â  â  âââ hostname
â  â  â  â  âââ hosts
â  â  â  â  âââ mtab -> /proc/mounts
â  â  â  â  âââ resolv.conf
â  â  â  âââ proc
â  â  â  âââ sys
â  â  âââ link
â  â  âââ lower
â  â  âââ work
â  â  âââ work
â  âââ l
â  âââ 2N57ZPCEPUQ3TVUAH5HY2M526N -> ../ffbbee81aeec171e1a70b27f3c3fc7ace6c0ca33dbfdd6d390b406d34b1c8b6d/diff
â  âââ ZOEHN3DWY3C3JS3UHQ634XJRAB -> ../114a646d7a311920e7ee0d958e6d480036303b7e9b220d056ac3823fb8d431bf/diff
âââ plugins
â  âââ storage
â  â  âââ blobs
â  â  âââ tmp
â  âââ tmp
âââ runtimes
âââ swarm
âââ tmp
âââ trust
âââ volumes
âââ 2ace0452ee4d6b6094ec704c3873843f6bb4e29c5d712241b15060da7d36e945
â  âââ _data
âââ metadata.db