ZFS telepítés és 2 lemez tükrözése

sudo apt install zfs-dkms -y
sudo apt install zfs-dkms -y

lsblk --ascii -o NAME,PARTUUID,LABEL,PATH,FSTYPE

sudo zpool create -f -o ashift=12 -m /home VDEV_NAME mirror /dev/disk/by-partuuid/DISK1_partuuid /dev/disk/by-partuuid/DISK2_partuuid

sudo zfs create VDEV_NAME/DATASET_NAME

zpool set cachefile=/etc/zfs/zpool.cache VDEV_NAME
systemctl enable zfs.target

zfs set relatime=on VDEV_NAME
zfs set compression=lz4 VDEV_NAME

sudo zpool status


# https://low-orbit.net/zfs-guide
# https://briankoopman.com/moving/
# https://pthree.org/2012/12/04/zfs-administration-part-i-vdevs/

Docker telepítés - Fix Docker mess Ubuntu 18.04

sudo apt purge docker.io docker-compose

sudo apt install docker.io docker-compose

docker-compose is already the newest version (1.17.1-2).

docker.io is already the newest version (19.03.6-0ubuntu1~18.04.1).

@whysthatso Just ran into this issue, could you please describe the full solution step by step? Do I need to uninstall docker-compose and stuff and then reinstall docker or what?

as far as i remember:

• uninstall everything docker-related
• check if there is /etc/systemd/system/docker.service, delete it
• install docker-compose

or it could be:

• uninstall everything docker-related

but yeah, sorry, i realized i should have contextualized my comment a bit better

• install docker-compose
• check if there is /etc/systemd/system/docker.service, delete it

try both, can't really mess anything up here

https://github.com/docker/compose/issues/6099

https://www.collabora.com/news-and-blog/blog/2018/07/04/docker-io-debian-package-back-to-life/

kwmartin commented

Needed all of: apt-get remove and re-install using curl as Kirill-Babkin suggests (and restart socker to be safe) add user to docker group using usermod sudo usermod -aG docker $USER logout and login undefine DOCKER_HOST (as suggested by rkazak at https://forums.docker.com/t/docker-commands-require-sudo/12987/2) which I had earlier set using > export DOCKER_HOST=127.0.0.1:2375 as suggested by jamethy and shin This was on an RPi 3B. After all of this, docker is now working. Is there any chance this could be cleaned up so others don't have to go through this painful experience, as it is experiences like this docker is designed to fix? Just a suggestion. https://github.com/docker/compose/issues/4181 sudo service docker restart