mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-25 01:37:55 +00:00
217f2e77f8
One of the last limitations when migrating a container using Podman's 'podman container checkpoint --export=/path/to/archive.tar.gz' was that it was necessary to manually handle changes to the container's root file-system. The recommendation was to mount everything as --tmpfs where the root file-system was changed. This extends the checkpoint export functionality to also include all changes to the root file-system in the checkpoint archive. The checkpoint archive now includes a tarstream of the result from 'podman diff'. This tarstream will be applied to the restored container before restoring the container. With this any container can now be migrated, even it there are changes to the root file-system. There was some discussion before implementing this to base the root file-system migration on 'podman commit', but it seemed wrong to do a 'podman commit' before the migration as that would change the parent layer the restored container is referencing. Probably not really a problem, but it would have meant that a migrated container will always reference another storage top layer than it used to reference during initial creation. Signed-off-by: Adrian Reber <areber@redhat.com> |
||
|---|---|---|
| .. | ||
| adapter | ||
| annotations | ||
| apparmor | ||
| cgroups | ||
| channelwriter | ||
| criu | ||
| ctime | ||
| errorhandling | ||
| firewall | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| logs | ||
| lookup | ||
| namespaces | ||
| netns | ||
| registrar | ||
| registries | ||
| resolvconf | ||
| rootless | ||
| spec | ||
| sysinfo | ||
| systemdgen | ||
| tracing | ||
| trust | ||
| util | ||
| varlinkapi | ||