Hi cmcfarland:
I'm not sure why the Windows Servers would be paused.
Here are some instructions on how to get docker service working again:
This procedure will get docker service working again but WILL WIPE OUT existing Docker Containers:
Stop and wipe all current docker files:
service docker stop
rm -rf /var/lib/docker/*
Try to mount:
zfs mount antlets/_docker
If the command above fails saying antlets/_docker doesn't exist, run:
zfs create antlets/_docker -o mountpoint=/var/lib/docker
check that /etc/docker/daemon.json contains
{ "storage-driver": "zfs" }
Start docker:
service docker start
Check docker using zfs
docker info | grep zfs
You can get the default docker images running the upgrade-antman command:
upgrade-antman
Make sure the docker service starts after a reboot
eL 2.0.0: systemctl enable docker
eL 0.x.x: rc-update add docker default
Hi cmcfarland:
I'm not sure why the Windows Servers would be paused.
Here are some instructions on how to get docker service working again:
This procedure will get docker service working again but WILL WIPE OUT existing Docker Containers:
Stop and wipe all current docker files:
service docker stop
rm -rf /var/lib/docker/*
Try to mount:
zfs mount antlets/_docker
If the command above fails saying antlets/_docker doesn't exist, run:
zfs create antlets/_docker -o mountpoint=/var/lib/docker
check that /etc/docker/daemon.json contains
{ "storage-driver": "zfs" }
Start docker:
service docker start
Check docker using zfs
docker info | grep zfs
You can get the default docker images running the upgrade-antman command:
upgrade-antman
Make sure the docker service starts after a reboot
eL 2.0.0: systemctl enable docker
eL 0.x.x: rc-update add docker default
danielgalvan has reacted to this post.