10:53 p.m.
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:
Thanks Daniel.
Will follow the steps you have suggested.
Thanks
On Sun, Dec 4, 2022, 3:24 PM Daniel Walsh <dwalsh(a)redhat.com> wrote:
> On 11/30/22 00:58, Lakshmi Mannuru wrote:
>
> Updated subject.
>
> On Tue, Nov 29, 2022, 11:57 PM Lakshmi Mannuru <
> lakshmi.mannuru17(a)gmail.com> wrote:
>
>> 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
>>
>>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
> 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.
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io