Difference between revisions of "AutoFS"
Jump to navigation
Jump to search
(Created page with "If you have AutoFS mount inside the container, you need to know some tricks. Category:HOWTO") |
Skinsbursky (talk | contribs) |
||
| Line 1: | Line 1: | ||
If you have AutoFS mount inside the container, you need to know some tricks. | If you have AutoFS mount inside the container, you need to know some tricks. | ||
| + | |||
| + | == Requirements == | ||
| + | |||
| + | Autofs migration is supported by criu starting from version ... | ||
| + | Another requirement is linux kernel with version 4.6 or higher. | ||
| + | |||
| + | == Limitations == | ||
| + | |||
| + | CRIU supports both direct (offset) and indirect AutoFS mount points migration. | ||
| + | |||
| + | Howewer, there is a limitation in migrating of systemd services, using AutoFS. | ||
| + | |||
| + | The problem is that systemd saves AutoFS mount point device ID in its internals and compares saved value with current one on each autofs-related request from kernel side. | ||
[[Category:HOWTO]] | [[Category:HOWTO]] | ||
Revision as of 14:45, 22 April 2016
If you have AutoFS mount inside the container, you need to know some tricks.
Requirements
Autofs migration is supported by criu starting from version ... Another requirement is linux kernel with version 4.6 or higher.
Limitations
CRIU supports both direct (offset) and indirect AutoFS mount points migration.
Howewer, there is a limitation in migrating of systemd services, using AutoFS.
The problem is that systemd saves AutoFS mount point device ID in its internals and compares saved value with current one on each autofs-related request from kernel side.