> On 30 Sep 2022, at 14:30, Nicola Mori wrote:
>
> # Save the long-running PID on file
> ps aux | grep "sleep infinity" | head -n 1 | awk '{ print $2 }' >
> /container-pipes-pid
echo $! >/container-pipes-pid
See man bash for $! definition.
Barry
Nice tip, thank you!
Nicola
On 02/10/22 09:43, Barry wrote:
On 30 Sep 2022, at 14:30, Nicola Mori wrote:
# Save the long-running PID on file
ps aux | grep "sleep infinity" | head -n 1 | awk '{ print $2 }' >
/container-pipes-pid
echo $! >/container-pipes-pid
See man bash for $!
Thanks for your insights. I have been able to workaround the problem
with a dirty hack:
- use this script as ENTRYPOINT:
# Start a long-running process to keep the container pipes open
sleep infinity < /proc/1/fd/0 > /proc/1/fd/1 2>&1 &
# Save the long-running PID on file
ps aux | grep
On Do, 29.09.22 19:42, Nicola Mori (nicolam...@aol.com) wrote:
> So I believe this problem might have been introduced by a systemd version
> subsequent to 219 and that hopefully it might be fixed somehow by means of
> e.g. proper configuration of the container/environment, but I need some
>
Hi,
On Thu, Sep 29, 2022 at 07:42:45PM +0200, Nicola Mori wrote:
> Hi,
> 3) Gitlab CI needs a shell running inside the container and attached to the
> container's STDIN/STDOUT
maybe it helps, when I did something similar the behavior of passing
"-it" to "docker run" or not could be unified by
Hi,
sorry in advance if I'm posting to the wrong list. I need to run systemd
inside a docker container and attach it to the container's stdin/stdout.
The reason for this weird request is the following:
1) I need to use the container for running Gilab CI jobs
2) the software being tested needs