Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman image scp fails due to ENOSPC on the remote server below /tmp without any error msg #21239

Closed
gurucubano opened this issue Jan 12, 2024 · 3 comments · Fixed by #21420
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@gurucubano
Copy link

Issue Description

Copy over an existing image from a RH server to a remote SuSE SLES server with

podman image scp c87c80c0911a srap57::

fails without any error message when on the remote host is not enough space below /tmp.

Steps to reproduce the issue

Steps to reproduce the issue

  1. podman system connection add srap57 ssh://[email protected]
  2. podman image scp c87c80c0911a srap57::
    Copying blob d5c1a9d0b1e5 done
    Copying blob 6859de28489f done
    Copying blob 35fb3b1b2123 done
    ...
    Writing manifest to image destination
    (shell prompt returned)

Describe the results you received

The above command does not end with something like
...
Loaded image:
sha256:9211bbaa0dbd68fed073065eb9f0a6ed00a75090a9235eca2554c62d1e75c58f

Describe the results you expected

I expected a message about the loaded image.

podman info output

source host:

Red Hat Enterprise Linux 8.9
podman version
Client:       Podman Engine
Version:      4.6.1
API Version:  4.6.1
Go Version:   go1.20.6
Built:        Mon Oct  9 18:15:55 2023
OS/Arch:      linux/amd64

destination host

SUSE Linux Enterprise Server 15 SP5
podman version
Client:       Podman Engine
Version:      4.7.2
API Version:  4.7.2
Go Version:   go1.21.4
Built:        Wed Nov  1 13:00:00 2023
OS/Arch:      linux/amd64

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

No

Additional environment details

image is around 6.1 GByte and on the destination host space below /tmp (where the sftp-server stores the temp. data):

df -kh /tmp
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/vg_root-lv_root   27G   19G  8.2G  70% /tmp

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@gurucubano gurucubano added the kind/bug Categorizes issue or PR as related to a bug. label Jan 12, 2024
@rhatdan
Copy link
Member

rhatdan commented Jan 12, 2024

The remote connection should be storing the data temporarily in the $TMPDIR directory, defaulting to /var/tmp.
I think this is a bug in Podman.

@rhatdan
Copy link
Member

rhatdan commented Jan 12, 2024

Interested in opening a PR to fix?

@gurucubano
Copy link
Author

On the target server side the TMPDIR used by the sftp-server can be modified with an entry like this in ~/.ssh/environment

TMPDIR=/where/ever/is/space/and/write/permitted

It remains as a bug that ENOSPC of the sftp-server is silently ignored.

@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label May 13, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants