h4de5
commented
3 years ago docker is running on my rpi4 with kodi and rpi0 with volumio. you can change the docker base path (the place where docker puts its images) to a non overlay/aufs mount.
some notes I put down - hopefully I helps you from here:
# places of docker.conf in kodi - may vary on other OS
vi ~/.kodi/addons/service.system.docker/config/docker.conf
vi ~/.kodi/userdata/addon_data/service.system.docker/config/docker.conf
# put ENV variables to change the docker path
DOCKER_DAEMON_OPTS="--data-root=/berryboot/docker"
DOCKER_STORAGE_OPTS="--storage-driver=overlay2 --storage-opt overlay2.override_kernel_check=1"
# restart docker daemon
systemctl restart docker
# not sure if still needed - change existing docker path
rm /var/lib/docker
ln -s /berryboot/docker /var/lib/docker
# systemd service in kodi
# cd ~/.kodi/addons/service.system.docker/system.d
# vi service.system.docker.service
I think docker doesn't work with berryboot. at least any image that I've tried have the same problem whenever I do docker run container.
I've tried libreelec, omv, nextcloudpi, dietpi, and various other images in berryboot, and the same aufs error comes up.
I admit I haven't tried berryboot in quite a while, after learning with docker one can pretty much run anything they want in an "empty" or a "simple" OS like Libreelec or dietpi, bare metal. But to me at least, the benefits of berryboot is huge.
So I was excited when I purchased a 256GB SSD an pi4, hoping to boot berryboot from it. Imagine the possibilities! But alas, after wrecking my head trying to figure out what I did wrong with berryboot, a realization quickly appeared in my head that it might be because of how berryboot does its thing.
With docker, a lot, if not all of the side effects/benefits of berryboot are negated.
Snapshots and backups are like containers... ish. Cloning is pretty similar. Restoring image is pretty much the same as well.
I'm considered to be a noob still, so I apologize if I sound harsh (I'm not, honest!) or demanding (more like a plea), so please, consider moving towards something - anything - that makes docker work (again? I can't remember).
Thanks and cheers for the splendid job! Berryboot really saved my a$$ billions of times before when learning about the wonderful world of Pi and Linux.
example $ ``` docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce Unable to find image 'portainer/portainer-ce:latest' locally latest: Pulling from portainer/portainer-ce b890dbc4eb27: Pull complete d39f4eb29d9f: Pull complete Digest: sha256:21713e42233ee953b4cd4e6e8b1e4b6c43ebe2ca1c2dc762824a1866fdb91d3e Status: Downloaded newer image for portainer/portainer-ce:latest docker: Error response from daemon: error creating aufs mount to /var/lib/docker/aufs/mnt/6f33100aa18d509a119efb492bb555f49d202bec72a29bc8a5cba0994e00942f-init: mount target=/var/lib/docker/aufs/mnt/6f33100aa18d509a119efb492bb555f49d202bec72a29bc8a5cba0994e00942f-init data=br:/var/lib/docker/aufs/diff/6f33100aa18d509a119efb492bb555f49d202bec72a29bc8a5cba0994e00942f-init=rw:/var/lib/docker/aufs/diff/71a64d0a64472fabf040dc1eefe20a4973b734062f2da0c3d7bcf6eb3ca71ad9=ro+wh:/var/lib/docker/aufs/diff/9257e5bc58b443c58c8a4a2bda0cf4d7d99b66850bd23966c252e990cf44d5e1=ro+wh,dio,xino=/dev/shm/aufs.xino: invalid argument. See 'docker run --help'.