Jarkko Sakkinen
jarkko
Each build seems to get a new #BTRFS subvolume at /var/lib/docker/btrfs/subvolumes. This will overtime exhaust the whole root file system. In order to disable this behavior, create /etc/docker/daemon.json with the contents:
{
"storage-driver": "overlay2"
}
I did not know this and neither could login to my system through GDM nor console. Luckily SSH login worked and I could delete all over 800 GB of subvolumes.
IMHO, objectively the default settings in #Docker are the worst ever.
1
0
1
@ikkeT did the switch to podman as the same build command-line and Dockerfile did not cause issues. Just wanted be cautious at first :-)
Apparently these also got pre-created (probably) by Debian package’s post-install script:
$ cat /etc/sub{uid,gid}
jarkko:100000:65536
jarkko:100000:65536
This is the first time in my life when I’m pro-actively using containers in my work so better to be still somewhat conservative in choices and take babysteps :-) Although it gives some lift that I know what naemspaces and cgroups are, and how they work.
1
0
1
```
$ podman images -qa
de5f96374006
6df894023726
```
Two is expected: docker.io/library/ubuntu:20.04 + R&D image. I don't really have opinions on container languages tbh :-) I use docker format because it is used by the keystone project. podman-unshare is just useful tool for what I do sometimes.
1
0
1
0
0
1
This would only make sense if you could optionally enable whatever it was doing for BTRFS because then you would know. Now it comes as a surprise, and not nice one for someone like me who had to use Docker for the 1st time in their life.
0
1
0
0
0
1