You should also usually get some sort of: Storing signaturesLoaded image(s): after Writing manifest to image destination if this doesn't show up, then the image doesn't actually get stored. I remember there being some compatibility issues over certain types/sizes of images w/ scp. Can you throw a `-v` in there to see if it tells you anything else? Charlie On Wed, Jan 10, 2024 at 9:33 AM Matthias Apitz <guru@unixarea.de> wrote:
I have an image on RH 8.x which runs fine (containing a SuSE SLES and PostgreSQL server):
$ podman images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/suse latest c87c80c0911a 26 hours ago 6.31 GB registry.suse.com/bci/bci-base 15.4 5bd0e4152d92 2 weeks ago 123 MB
I created a connection to another host as:
$ podman system connection list Name URI Identity Default srap57 ssh:// apitzm@srap57dxr1.dev.xxxxxx.org:22/run/user/200007/podman/podman.sock true
To the other host I can SSH fine based on RSA public/private keys and podman is installed there to:
$ ssh apitzm@srap57dxr1.dev.xxxxxx.org Last login: Wed Jan 10 14:05:12 2024 from 10.201.64.28 apitzm@srap57dxr1:~> 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
When I now copy over the image with:
$ podman image scp c87c80c0911a srap57::
it transfers the ~6 GByte (I can see them in /tmp as a big tar file of tar files) and at the end it says:
... Writing manifest to image destination $
(i.e. the shell prompt is there again)
But on srap57dxr1.dev.xxxxxx.org I can't see anything of the image at the end.
What I've done wrong?
Thanks
matthias
-- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland. _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io