Modifying Shutdown Sequence (Stop LXC's prior to Networking)

C

_chris

New Member
Dec 31, 2023
1
0
1
Does anyone have suggestions for modifying the shutdown process? It would seem that Prox (8.1.3 and others) drop elements of the networking and NFS mounts before stopping the running LXC's. Due to this current order the automated shutdown of the lxc's can take 300 plus seconds to timeout and force stop if an nfs mount point is used in the lxc.

Is there a way to latch onto say mnt-remote.mount to say don't stop until pve-manager (or similar) is fully stopped?
 
Last edited:
_chris said:
Does anyone have suggestions for modifying the shutdown process? It would seem that Prox (8.1.3 and others) drop elements of the networking and NFS mounts before stopping the running LXC's. Due to this current order the automated shutdown of the lxc's can take 300 plus seconds to timeout and force stop if an nfs mount point is used in the lxc.

Is there a way to latch onto say mnt-remote.mount to say don't stop until pve-manager (or similar) is fully stopped?
Click to expand...
Fair question, having the same issue myself.

Using containers that use NFS mounts inside them, and they refuse to stop or shutdown, have to kill the "lxc-start" to get them to die. Welcome any suggestions.
 
You must log in or register to reply here.
Top Bottom