6:49 a.m.
Pavel,
I'm confused - was there supposed to be a problem? Podman worked
straight away for me . . I installed the KDE version so I could use
Wayland but then got Sway going . . wait, now that I think about it . .
I think I had to rebuild my Rails Watched Netflix Video container - I
keep all the stuff I want to keep under /home (/dev/sda5) so I don't
lose anything when upgrading /dev/sd[1-4] to a new Fedora version . .
Phil.
On 2021-08-25 21:30, Pavel Sosin wrote:
I can confirm that the Podman 3.2 on Fedora 34 workstation does
work.
I had "luck" to reinstall everything from scratch after an attempt to
upgrade a machine to Win 11 completely destroyed one of the laptops
in my home.
Yes, it works, the role of the user's systemd manager in cgroup
management is clear to me: User's systemd must be activated by the
pam/logind to create a consistent environment, create user's service,
and initialyze user's session including /run/user, ... But the
documentation is confusing anyway: The in-line comments in the
/usr/share/containers/containers.conf without a single example can't
replace the documentation.
TCP sockets in the IPV6 local networks, Does gateway IP as network
manager metter?
#Path to look valid OCI runtime: crun. runc, runcd, kata, ??? There
are no explanations or links to the documentation. In the Kata
documentation Podman as a container manager is not mentioned, only
Kubernetes and Docker What are the differences ?
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au