Currently vyOs uses the vfs storage driver for podman storage, which is intended for testing purposes. We could use the much more space efficient overlay driver instead.
Description
Description
Details
Details
- Version
- 1.4
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Performance optimization
Related Objects
Related Objects
- Mentioned In
- T5401: Using load config restarts containers every time
T5365: Container systemd units require authentication
rVYOSONEXf3956a5358a7: container: T4870: remove manual user interaction during storage migration
rVYOSONEX6fe49566313f: container: T4870: update to overlay2 driver
rVYOSONEX60c80df479c0: container: T4870: bump package version 0 -> 1 for filesystem change
rVYOSONEX9c891c723737: container: T4870: bump package version 0 -> 1 for filesystem change
rVYOSONEXf07c2071129b: container: T4870: Update to overlay driver
rVYOSONEX40efa3e7284c: Merge pull request #1702 from TGNThump/patch-1 - Mentioned Here
- rVYOSONEXf3956a5358a7: container: T4870: remove manual user interaction during storage migration
Event Timeline
Comment Actions
The "incompatibility" can be resolved by running the following script prior to upgrading to a new image:
#!/bin/sh # Migration helper script needed to be executed before upgrading to a more # recent VyOS version as the container storage driver is changed incompatible for pod in $(cli-shell-api listActiveNodes container name); do systemctl stop vyos-container-${pod//\'}.service done sed -i 's/vfs/overlay2/g' /etc/containers/storage.conf /usr/share/vyos/templates/container/storage.conf.j2 rm -rf /usr/lib/live/mount/persistence/container/storage/libpod for pod in $(cli-shell-api listActiveNodes container name); do image=$(cli-shell-api returnActiveValue container name ${pod//\'} image) podman image pull $image systemctl start vyos-container-${pod//\'}.service done for dir in vfs vfs-containers vfs-images vfs-layers; do rm -rf /usr/lib/live/mount/persistence/container/storage/$dir done
Comment Actions
This manual step just got removed by f3956a5358a71 which simply exports active images as oci-image and re-imports the image after the filesystem got migrated. No manual interaction by the user required.