You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
podman-remote (actually the varlink server) is not cleaning up after itself; it leaves a buildTarballXXXX directory and varlink_sendXXXX file in tmpdir:
# mkdir /t/podman-remote-tmp
# TMPDIR=/t/podman-remote-tmp /path/to/podman varlink --timeout=0 &
# ls -l /t/podman-remote-tmp
total 0
# /path/to/podman-remote build -t build_test --format=docker /path/to/some/dir
....
# ls -l /t/podman-remote-tmp
total 4
drwx------. 2 root root 60 Aug 21 11:16 buildTarball217054436
-rw-------. 1 root root 2048 Aug 21 11:16 varlink_send476368217
The text was updated successfully, but these errors were encountered:
when performing an image build over a varlink connection, we should
clean up tmp files that are a result of sending the file to the host and
untarring it for the build.
Fixes: containers#3869
Signed-off-by: baude <[email protected]>
when performing an image build over a varlink connection, we should
clean up tmp files that are a result of sending the file to the host and
untarring it for the build.
Fixes: containers#3869
Signed-off-by: baude <[email protected]>
podman-remote (actually the varlink server) is not cleaning up after itself; it leaves a
buildTarballXXXX
directory andvarlink_sendXXXX
file in tmpdir:The text was updated successfully, but these errors were encountered: