26
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: − === <code>docker ps, stop, kill</code> === and === <code>logs</code> ===+ − + − === <code>docker restore</code> === commands.+ − === <code>docker ps, stop, kill </code> === and === <code>logs</code> ===+ − Line 34:
Line 33: − + −
no edit summary
container has exited. After restore, the Docker daemon doesn't know that
container has exited. After restore, the Docker daemon doesn't know that
the container is running again. Therefore, commands such as
the container is running again. Therefore, commands such as
<code>docker ps, stop, kill</code> and <code>logs</code>
will not work correctly.
will not work correctly.
External C/R was done as a proof-of-concept.
External C/R was done as a proof-of-concept.
'''Native C/R''' using the newly added === <code>docker checkpoint</code> === and
'''Native C/R''' using the newly added <code>docker checkpoint</code> and
<code>docker restore</code> commands.
Because the Docker daemon is involved in both checkpoint and restore,
Because the Docker daemon is involved in both checkpoint and restore,
its notion of the container state will be consistent and all commands such as
its notion of the container state will be consistent and all commands such as
<code>docker ps, stop, kill </code> and <code>logs</code> will work.
will work.
This is obviously the preferred method of checkpointing and restoring Docker containers.
This is obviously the preferred method of checkpointing and restoring Docker containers.
For native C/R support, additional functionality was added to CRIU.
For native C/R support, additional functionality was added to CRIU.
The most notable addition is the === <code>--inherit-fd</code> ===
The most notable addition is the <code>--inherit-fd</code> command line option.
command line option.
== External C/R ==
== External C/R ==