in executor v2.29.2, podman ps does not work
oswalpalash opened this issue · comments
Describe the bug
In the newly released version of the executor container, v2.29.2
the podman commands seem to not work.
ps auxf
shows podman processes running, but podman ps
does not show the running containers.
To Reproduce
Steps to reproduce the behavior:
- Trigger a remote build with
v2.29.2
container, I used this genrule:
genrule(
name = "temp",
outs = ["temp.txt"],
cmd = """
sleep 100000
""",
exec_properties = {
# "workload-isolation-type": "firecracker",
},
)
- Exec into the RBE parent executor container, and do
podman ps
and it shows no containers.
Expected behavior
podman
cli to work.
Screenshots
If applicable, add screenshots to help explain your problem.
I wonder if this is caused by the container started with a different uid ($user) than the current uid of your shell.
Does "podman ps --all" show anything?
@sluongng that doesn't list the procs either.
It seems like podman --transient-store ps
should work.
The flag allows us to start the container much faster, but the container information is stored in a different place that is incompatible with normal operation.