3
- System(root)-run and User-run containers are isolated.
4
* Root configuration is in /etc/containers. With default location for containers in /var/lib/containers
5
* User configuration in ~/.config/containers and storage is in ~/.local/share/containers/
9
- On RHEL selection of storage engine boils down to 'overlay' (overlay2 in docker) or 'vfs'
10
* btrfs is not supported by RHEL (deprecated and support not planed: never reach maturity and other technologies more-or-less catch up with feature set)
11
* devicemapper is not supported by podman (unclear why)
12
- System and users may use different storage engines.
13
- OverlayFS still problematic in some cases.
14
* Rsync'ing large folder within the file system is extremely slow (< 1 MB/s). eix-sync takes forever. However, copying data from internet is quite fast.
15
* VFS works just fine in such cases
16
- The storage driver is configured in containers/storage.conf (driver=vfs)
17
* Current driver could be found with 'podman info' (GraphDriverName)
18
* The configured value will be silently ignored if the 'storage' folder was already intialized with different driver
19
* So that the changes in storage.conf take effect, it is necessary to remove all files there (/var/lib/containers/storage)
20
- The following configuration is necessary if devicemapper ocasionaly gets supported (and it works rather well on KaaS v.1 platform)
22
[storage.options.thinpool]
23
directlvm_device = "/dev/sdb"
24
directlvm_device_force = "True" # Rewrite data if partitions already existing on the specified device
29
- The containers can be easily demonized using systemd services
33
TimeoutStartSec=5m # Give enough time to download and start
34
ExecStartPre=-/usr/bin/podman rm "distcc" # Delete old container
35
ExecStart=/usr/bin/podman run --name distcc -p 3632:3632 chsa/distcc:latest # Start command
36
ExecReload=-/usr/bin/podman stop "distcc"
37
ExecReload=-/usr/bin/podman rm "distcc"
38
ExecStop=-/usr/bin/podman stop "distcc"
45
- Format '-p 0.0.0.0:80:80' is not working for some reason.
46
* The telnet to ':80' is working, but actualy communication for some reason is not happening
47
* '-p 80:80' has no problems
48
- PTRACE operation not permited
49
* Run containers with '--privileged' option