12:57 a.m.
Hi Team,
I have a scenario where I need some help.
The application is having multiple containers running with podman run at
start up.
When firmware update is triggered, some of the files running on x
container, need to start tftp container. Can some suggest the steps to
start and stop tftp container from x container when Firmware update is
getting executed.
Thanks in advance for your help.
Thank you
4:23 p.m.
New subject: start and stop the container from another container
On 11/30/22 00:58, Lakshmi Mannuru wrote:
You would need to leak into the monitoring container /run and the
directory where the containers are stored.
$home/.local/containers and mount them on /run and
$HOME/.local/containers at the same spot in a --privileged container,
now podman inside of the container could restart the container.
Alternatively you could mount in $XDG_RUNTIME_DIR/podman/podman.spock
into a container with selinux turned off (--security-opt label=disable)
Then use podman --remote inside the container to restart the contaner on
the host.
11:53 p.m.
New subject: start and stop the container from another container
Hi Lakshmi,
I really thought about whether to answer or not. But firmware update,
containers starting other containers. That sounds like you’re writing your
own container-based init system.
If you do that in production, please use
https://silverblue.fedoraproject.org
There’s a special place in hell reserved for people who run their
hand-crafted container init systems in production. Never do that. It’s
simply too complicated to get it right with just one pair of eyes.
If you do that for your Raspi that collects your smart home metrics, fine.
Everybody needs a hobby.
Best
Erik
PS: Special hell! ;)
Lakshmi Mannuru <lakshmi.mannuru17(a)gmail.com> schrieb am Mo. 5. Dez. 2022
um 03:49:
851
days inactive
856
days old
4 comments
3 participants
participants (3)
-
Daniel Walsh -
Erik Bernoth -
Lakshmi Mannuru