suspend container to disk

[ffa]

Hi,
Could the docker checkpoint command be exposed, so users may "suspend" and "resume" running applications?

[timthelion]

Unfortunately, I don't know if this is possible. I read somewhere, that it is not possible to use the suspend command with unix sockets, which subuser uses in order to set up the xpra-x11 bridge. Is the reason that you want this, in order to save the state of the application, or in order to improve startup times?

…

On 02/26/2017 11:17 PM, Adam wrote: Hi, Could the docker |checkpoint| command be exposed, so users may "suspend" and "resume" running applications? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#315>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABU7-AJ6UwIsD5rynnkRha_WRGtt47Osks5rgfnxgaJpZM4MMivr>.

[ffa]

Save the state of applications. (though this does aid in the startup time issue as well)

Maybe the xpra-x11 bridge can be closed before checkpointing and reopened before restoring?

A per container suspend to disk is much more useful then a system wide suspend to disk. A system wide suspend to disk is much more faulty because of the large interdependencies for system restore. Furthermore, it is intolerant to system updates and changes. On the other hand, a per container suspend to disk solves most of these issues or alleviates them to a large degree.

[timthelion]

I can try to think about this, and of course you can try to play with this too. I would accept a good pull request. But this isn't a priority for me now, and I will not be able to specially devote my time to this issue.

[ffa]

okay