[lxc-users] Marking running containers as emphermial
Fajar A. Nugraha
list at fajar.net
Tue Sep 12 06:29:32 UTC 2017
On Tue, Sep 12, 2017 at 3:16 AM, Dave Smith <dave.smith at candata.com> wrote:
> I have an application that I am running as a single process in an lxc
> container . The process is serving websocket requests from an upstream
> proxy. What I would like to do is when we do an update , we launch a new
> container , update the proxy to point to the updated container and then
> tell the old container to destroy itself on shutdown. The actual process in
> the old container will be told to shutdown once it has no client
> connections thus shutting the container down.
>
>
That looks exactly like the default 'rolling' deployment strategy in
openshift, with 'proxy' being the openshift-managed haproxy. You might want
to look at that (even though they don't support lxc).
> I have tried to use the lxc.hook.post-stop. The script checked to see if
> a file was on the root file system and then called lxc-destroy but the
> process just hung. Is there a way for a container config to be updated
> when it is running or is there another to go about this.
>
>
Not that I know of.
--
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20170912/78e7f410/attachment.html>
More information about the lxc-users
mailing list