Repository for podman.io website using GitHub Pages.
Home Page: https://podman.io
License: Other
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
All pages linked from http://docs.podman.io/en/latest/Commands.html have the same title: "NAME - Podman documentation". This shows up in browser tabs, as well as in search results.
The search results would be much easier to navigate if they prominently showed the command names. Having clear titles for each page is also helpful when keeping multiple tabs open for reference.
Steps to reproduce the issue:
Describe the results you received:
Step 2: Browser tab shows title "NAME - Podman documentation":
Step 5: Results given are all titled "NAME":
Describe the results you expected:
Step 2: Browser tab shows title (eg) "podman-info - Podman documentation"
Step 5: Search result links show the command name so it's clear which page they link to.
The instruction to get the source code sounds strange for a project that uses go modules. Is it still actual? What is the minimal go version for building podman 1.9.x?
runc is no longer needed in a Fedora, Centos or RHEL "Install from Scratch and should be removed from the yum installation step there. https://podman.io/getting-started/installation#build-and-run-dependencies
Hi,
I've been trying to install Podman 2.2 according to the installation instructions but so far I've been unsuccessful. Here are the current instructions:
# Raspbian 10
# Use buster-backports on Rasbian 10 for a newer libseccomp2
echo 'deb http://deb.debian.org/debian buster-backports main' >> /etc/apt/sources.list
echo 'deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Raspbian_10/ /' | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Raspbian_10/Release.key | sudo apt-key add -
sudo apt-get update -qq
sudo apt-get -qq -y install podman
I've hit 2 different issues.
Neither of my rpis had the signing key for buster-backports available. apt complained when I tried to update the cache:
Err:1 http://deb.debian.org/debian buster-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
I was able to workaround this problem by first manually installing debian-archive-keyring_2019.1_all.deb. It might be useful to include that step in the instructions.
Once the backports are set up I still can't install podman 2.2:
# apt-get install podman
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
podman : Depends: libseccomp2 (>= 2.4.3-1) but 2.3.3-4 is to be installed
E: Unable to correct problems, you have held broken packages.
I'm not sure where to look for the proper version of libseccomp2.
Howdy!
I am missing some configuration files after building from source (seccomp.json, mounts.conf). I have tried following the guide located at https://podman.io/getting-started/installation , but am unable to get these files because the provided links are dead. I am not very knowledgeable, so I do not know where to find these files elsewhere. Do you mind providing them to me?
Thanks!
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Sort of, I guess.
Description
The install instruction on https://podman.io/getting-started/installation for Raspberry Pis recommend using the Kubic project repositories. Unfortunately the maintainer has announced to not support "old" distros anymore: https://podman.io/blogs/2021/03/02/podman-support-for-older-distros.html
So there will be no podman > 3.0 for Raspberry Pi OS for the foreseeable future.
The hint about switching to a newer distro version and that podman will be part of Debian 11 is only marginally helpful, because there is no release date for Debian 11 announced yet and it will take even longer until it will make it to the Raspis.
Even worse, the podman version currently in testing (i.e. most likely going to be new stable) is 3.0.1, so Debian 11 users are probably going to be stuck with some version of 3.0 for quite some time.
Debian unstable is currently also shipping 3.0.1, but I'm somewhat optimistic that they will follow the development more closely and will hopefully update to 3.1 in the near future.
All in all it might be wise to think about what should be done about the install instructions when podman moves further away from 3.0 and when, hopefully, Debian Unstable follows somewhat closely.
I've been quite successful with the following approach:
cat /etc/apt/sources.list.d/unstable.list
deb http://deb.debian.org/debian/ unstable main contrib non-free
cat /etc/apt/preferences.d/99-prio
Package: *
Pin: release a=buster-backports
Pin-Priority: 90
Package: *
Pin: release a=unstable
Pin-Priority: 80
Unfortunately I cannot say if that works if you start from scratch, because I still have the Kubic repos installed, so I'm currently running a bit of an unhealthy mix of Debian Unstable (podman 3.0) and Kubic (slirp4netns 1.1 instead of 1.0 from Debian Unstable).
Also I do not quite like to tear down my systems and give it a fresh start, because my Raspis are actually supposed to be doing work and are not really meant for testing.
So if there is someone with an idle Raspi, maybe they can give it a try.
it seems dead links are not checked when changes are pushed to this repository, or at least there isn't a job doing that regularly, because I can easily find some. ;) I don't remember the ones I found the last time (and unfortunately did not report), but today I found two in the whatis page:
There might be other dead links on the site worth fixing.
I get get a link to page section only be looking at the source code, like https://podman.io/getting-started/installation#get-source-code It would be much more convenient if headers contained the anchors.
hi,
when I try to install podman for the first time on ubuntu 19.10
following the documentation
got this error
sudo apt-get update -qq
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_ Release' does not have a Release file.
W: GPG error: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_19.10 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_19.10 InRelease' is not signed.
It seems provided installation steps for Amazon Linux 2 are incomplete.
After adding kubic repo and running yum install podman it throws message about missing container-selinux dependency:
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
devel_kubic_libcontainers_stable | 1.3 kB 00:00:00
devel_kubic_libcontainers_stable/primary | 9.8 kB 00:00:00
devel_kubic_libcontainers_stable 27/27
2 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package podman.x86_64 0:1.8.1-2.1.el7 will be installed
--> Processing Dependency: podman-plugins = 1.8.1-2.1.el7 for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: slirp4netns >= 0.3.0-2 for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: containernetworking-plugins >= 0.7.5-1 for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: runc for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: nftables for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: containers-common for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: container-selinux for package: podman-1.8.1-2.1.el7.x86_64
--> Processing Dependency: conmon for package: podman-1.8.1-2.1.el7.x86_64
--> Running transaction check
---> Package conmon.x86_64 2:2.0.11-1.1.el7 will be installed
---> Package containernetworking-plugins.x86_64 0:0.8.5-11.1.el7 will be installed
---> Package containers-common.x86_64 2:0.1.41-7.1.el7 will be installed
---> Package nftables.x86_64 1:0.9.0-14.amzn2.0.1 will be installed
--> Processing Dependency: libnftnl.so.11(LIBNFTNL_11)(64bit) for package: 1:nftables-0.9.0-14.amzn2.0.1.x86_64
--> Processing Dependency: libnftnl.so.11()(64bit) for package: 1:nftables-0.9.0-14.amzn2.0.1.x86_64
---> Package podman.x86_64 0:1.8.1-2.1.el7 will be installed
--> Processing Dependency: container-selinux for package: podman-1.8.1-2.1.el7.x86_64
---> Package podman-plugins.x86_64 0:1.8.1-2.1.el7 will be installed
---> Package runc.x86_64 0:1.0.0-0.1.20190510.git2b18fe1.amzn2 will be installed
---> Package slirp4netns.x86_64 0:0.4.3-22.1.el7 will be installed
--> Running transaction check
---> Package libnftnl.x86_64 0:1.1.1-4.amzn2 will be installed
---> Package podman.x86_64 0:1.8.1-2.1.el7 will be installed
--> Processing Dependency: container-selinux for package: podman-1.8.1-2.1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: podman-1.8.1-2.1.el7.x86_64 (devel_kubic_libcontainers_stable)
Requires: container-selinux
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I started my podman with the following installation steps.
$ sudo apt install dirmngr \
software-properties-common
$ sudo add-apt-repository \
ppa:projectatomic/ppa
$ sudo apt update
$ sudo apt install -y podman buildah skopeodid not find /etc/containers/registries.conf.
and got this echo.
$ podman -v
podman version 1.5.0
WARN[0000] unable to find /etc/containers/registries.conf. some podman (image shortnames) commands may be limitedHere are my system info:
$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
$ uname -a
Linux alihk149 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
After following the Ubuntu apt installation instructions on Pop!_OS, when running podman (without arguments) or podman pull path/to/docker, I am presented with the error:
Error: default OCI runtime "runc" not found: invalid argument
The solution for me was to also run: sudo apt install runc, but it took me a moment to realize it, is this something that can be added to the documentation?
Note: This is an observation from using Pop!_OS, I would have to check if this also applies to Ubuntu and Debian.
Thanks!
Was trying to do an update on my Ubuntu machine:
Err:6 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04 InRelease
The following signatures were invalid: EXPKEYSIG 4D64390375060AA4 devel:kubic OBS Project devel:[email protected]
Hi,
when running rootless containers, I am getting some errors:
podman run -dt -p 8080:80 docker.io/library/httpd:2.4
ERRO[0000] unable to write pod event: "open : no such file or directory"
ERRO[0000] unable to write pod event: "open : no such file or directory"
ERRO[0000] unable to write pod event: "open : no such file or directory"
These kind of errors occur for several subcommands like: run, stop, start, restart
Other subcommands like "ps" seem not to be affected.
Disabling SELinux does not help to prevent the errors.
OS: Fedora 32 Silverblue
Podman: 1.9.1
If you need any additional information, please feel free to reach out to me.
https://podman.io/getting-started/installation says
# Debian 10
# Use buster-backports on Debian 10 for a newer libseccomp2
echo 'deb http://deb.debian.org/debian buster-backports main' >> /etc/apt/sources.list
echo 'deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/Debian_10/ /' > /etc/apt/sources.list.d/devel:kubic:libcontainers:testing.list
curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/Debian_10/Release.key | sudo apt-key add -
sudo apt-get update -qq
sudo apt-get -qq -y install podmanThis produces the error
The following packages have unmet dependencies:
podman : Depends: libseccomp2 (>= 2.4.3-1) but 2.3.3-4 is to be installed
The probably missing command is
apt-get -y -t buster-backports install libseccomp2I followed the podman installation instructions at
https://podman.io/getting-started/installation
but it fails on this step
[test@centos8 ~]$ sudo dnf -y install podman
CentOS-8 - AppStream 11 MB/s | 6.8 MB 00:00
CentOS-8 - Base 14 MB/s | 6.0 MB 00:00
CentOS-8 - Extras 20 kB/s | 5.5 kB 00:00
Copr repo for container-selinux owned by rhcontainerbot 3.7 kB/s | 1.3 kB 00:00
Stable Releases of Upstream github.com/containers packages (CentOS_8) 129 kB/s | 56 kB 00:00
Dependencies resolved.
============================================================================================================================================================================================================
Package Architecture Version Repository Size
============================================================================================================================================================================================================
Installing:
podman x86_64 1.9.0-2.1.el8 devel_kubic_libcontainers_stable 23 M
Installing dependencies:
container-selinux noarch 2:2.124.0-1.module_el8.1.0+272+3e64ee36 AppStream 47 k
criu x86_64 3.12-9.el8 AppStream 482 k
libnet x86_64 1.1.6-15.el8 AppStream 67 k
protobuf-c x86_64 1.3.0-4.el8 AppStream 37 k
checkpolicy x86_64 2.9-1.el8 BaseOS 348 k
policycoreutils-python-utils noarch 2.9-3.el8_1.1 BaseOS 250 k
python3-audit x86_64 3.0-0.13.20190507gitf58ec40.el8 BaseOS 85 k
python3-libsemanage x86_64 2.9-1.el8 BaseOS 127 k
python3-policycoreutils noarch 2.9-3.el8_1.1 BaseOS 2.2 M
python3-setools x86_64 4.2.2-1.el8 BaseOS 600 k
conmon x86_64 2:2.0.15-2.2.el8 devel_kubic_libcontainers_stable 39 k
containernetworking-plugins x86_64 0.8.5-145.2.el8 devel_kubic_libcontainers_stable 35 M
containers-common x86_64 2:0.2.0-2.2.el8 devel_kubic_libcontainers_stable 57 k
libvarlink-util x86_64 19-1.2.el8 devel_kubic_libcontainers_stable 51 k
podman-plugins x86_64 1.9.0-2.1.el8 devel_kubic_libcontainers_stable 2.3 M
runc x86_64 2:1.0.0-15.3.el8 devel_kubic_libcontainers_stable 4.6 M
slirp4netns x86_64 0.4.3-23.3.el8 devel_kubic_libcontainers_stable 90 k
Installing weak dependencies:
tar x86_64 2:1.30-4.el8 BaseOS 838 k
Transaction Summary
============================================================================================================================================================================================================
Install 19 Packages
Total download size: 71 M
Installed size: 204 M
Downloading Packages:
(1/19): container-selinux-2.124.0-1.module_el8.1.0+272+3e64ee36.noarch.rpm 911 kB/s | 47 kB 00:00
(2/19): libnet-1.1.6-15.el8.x86_64.rpm 1.3 MB/s | 67 kB 00:00
(3/19): protobuf-c-1.3.0-4.el8.x86_64.rpm 2.8 MB/s | 37 kB 00:00
(4/19): criu-3.12-9.el8.x86_64.rpm 5.7 MB/s | 482 kB 00:00
(5/19): python3-audit-3.0-0.13.20190507gitf58ec40.el8.x86_64.rpm 1.6 MB/s | 85 kB 00:00
(6/19): policycoreutils-python-utils-2.9-3.el8_1.1.noarch.rpm 3.3 MB/s | 250 kB 00:00
(7/19): checkpolicy-2.9-1.el8.x86_64.rpm 3.9 MB/s | 348 kB 00:00
(8/19): python3-libsemanage-2.9-1.el8.x86_64.rpm 3.9 MB/s | 127 kB 00:00
(9/19): python3-setools-4.2.2-1.el8.x86_64.rpm 12 MB/s | 600 kB 00:00
(10/19): tar-1.30-4.el8.x86_64.rpm 17 MB/s | 838 kB 00:00
(11/19): python3-policycoreutils-2.9-3.el8_1.1.noarch.rpm 22 MB/s | 2.2 MB 00:00
(12/19): conmon-2.0.15-2.2.el8.x86_64.rpm 205 kB/s | 39 kB 00:00
(13/19): containers-common-0.2.0-2.2.el8.x86_64.rpm 361 kB/s | 57 kB 00:00
(14/19): libvarlink-util-19-1.2.el8.x86_64.rpm 386 kB/s | 51 kB 00:00
(15/19): containernetworking-plugins-0.8.5-145.2.el8.x86_64.rpm 59 MB/s | 35 MB 00:00
(16/19): runc-1.0.0-15.3.el8.x86_64.rpm 23 MB/s | 4.6 MB 00:00
(17/19): podman-plugins-1.9.0-2.1.el8.x86_64.rpm 3.9 MB/s | 2.3 MB 00:00
(18/19): slirp4netns-0.4.3-23.3.el8.x86_64.rpm 681 kB/s | 90 kB 00:00
(19/19): podman-1.9.0-2.1.el8.x86_64.rpm 11 MB/s | 23 MB 00:02
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 24 MB/s | 71 MB 00:02
Running transaction check
No available modular metadata for modular package 'container-selinux-2:2.124.0-1.module_el8.1.0+272+3e64ee36.noarch', it cannot be installed on the system
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: No available modular metadata for modular package
[test@centos8 ~]$
I've tried to run dnf clean packages as suggested above, but it didn't help.
Computer architecture: x86_64
Here is the output from the command sudo dnf repolist -v:
[test@centos8 ~]$ sudo dnf repolist -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.7
cachedir: /var/cache/dnf
repo: using cache for: AppStream
AppStream: using metadata from Tue Apr 14 03:06:48 2020.
repo: using cache for: BaseOS
BaseOS: using metadata from Tue Apr 14 03:06:08 2020.
repo: using cache for: extras
extras: using metadata from Tue Apr 14 21:44:23 2020.
repo: using cache for: copr:copr.fedorainfracloud.org:rhcontainerbot:container-selinux
copr:copr.fedorainfracloud.org:rhcontainerbot:container-selinux: using metadata from Thu Apr 16 13:07:28 2020.
repo: using cache for: devel_kubic_libcontainers_stable
devel_kubic_libcontainers_stable: using metadata from Thu Apr 16 16:51:32 2020.
Last metadata expiration check: 0:00:38 ago on Thu Apr 16 17:10:46 2020.
Completion plugin: Generating completion cache...
Repo-id : AppStream
Repo-name : CentOS-8 - AppStream
Repo-revision: 1586826408
Repo-updated : Tue Apr 14 03:06:48 2020
Repo-pkgs : 5298
Repo-size : 8.1 G
Repo-mirrors : http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock
Repo-baseurl : http://mirror.zetup.net/CentOS/8.1.1911/AppStream/x86_64/os/ (9 more)
Repo-expire : 172800 second(s) (last: Thu Apr 16 17:10:41 2020)
Repo-filename: /etc/yum.repos.d/CentOS-AppStream.repo
Repo-id : BaseOS
Repo-name : CentOS-8 - Base
Repo-revision: 1586826368
Repo-updated : Tue Apr 14 03:06:08 2020
Repo-pkgs : 2231
Repo-size : 2.1 G
Repo-mirrors : http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=BaseOS&infra=stock
Repo-baseurl : http://mirror.nsc.liu.se/CentOS/8.1.1911/BaseOS/x86_64/os/ (9 more)
Repo-expire : 172800 second(s) (last: Thu Apr 16 17:10:43 2020)
Repo-filename: /etc/yum.repos.d/CentOS-Base.repo
Repo-id : copr:copr.fedorainfracloud.org:rhcontainerbot:container-selinux
Repo-name : Copr repo for container-selinux owned by rhcontainerbot
Repo-revision: 1587035248
Repo-updated : Thu Apr 16 13:07:28 2020
Repo-pkgs : 2
Repo-size : 87 k
Repo-baseurl : https://download.copr.fedorainfracloud.org/results/rhcontainerbot/container-selinux/epel-8-x86_64/
Repo-expire : 172800 second(s) (last: Thu Apr 16 17:10:45 2020)
Repo-filename: /etc/yum.repos.d/_copr:copr.fedorainfracloud.org:rhcontainerbot:container-selinux.repo
Repo-id : devel_kubic_libcontainers_stable
Repo-name : Stable Releases of Upstream github.com/containers packages (CentOS_8)
Repo-revision: 1587048692
Repo-updated : Thu Apr 16 16:51:32 2020
Repo-pkgs : 71
Repo-size : 303 M
Repo-baseurl : http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/
Repo-expire : 172800 second(s) (last: Thu Apr 16 17:10:46 2020)
Repo-filename: /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo
Repo-id : extras
Repo-name : CentOS-8 - Extras
Repo-revision: 1586893465
Repo-updated : Tue Apr 14 21:44:23 2020
Repo-pkgs : 15
Repo-size : 187 k
Repo-mirrors : http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=extras&infra=stock
Repo-baseurl : http://mirror.zetup.net/CentOS/8.1.1911/extras/x86_64/os/ (9 more)
Repo-expire : 172800 second(s) (last: Thu Apr 16 17:10:44 2020)
Repo-filename: /etc/yum.repos.d/CentOS-Extras.repo
Total packages: 7617
[test@centos8 ~]$
Audit reports following selinux error, when java is trying to create unix socket to /tmp.
type=AVC msg=audit(1590489952.995:140737): avc: denied { create } for pid=23087 comm=417474616368204C697374656E6572 name=".java_pid63.tmp" scontext=system_u: system_r:container_t:s0:c522,c777 tcontext=system_u:object_r:fusefs_t:s0 tclass=sock_file permissive=
Podman has been configured to use fuse-overlayfs. User has custom runroot and graphroot, which have following selinux types:
graphroot: drwxr-xr-x. someuser someuser unconfined_u:object_r:data_home_t:s0 lib
runroot: drwxrwxrwt. someuser someuser unconfined_u:object_r:user_tmp_t:s0 run
podman: version 1.6.4
container-selinux: version 2.119.1
fusermount3 version: 3.6.1
fuse-overlayfs: version 0.7.2
FUSE library version 3.6.1
using FUSE kernel interface version 7.29
Python script for testing socket creation inside container:
import socket; socket.socket(socket.AF_UNIX, socket.SOCK_STREAM).bind("/tmp/test.sock")
Binding a local filesystem to /tmp fixes issue. This solution however leaves us responsible for clearing contents of container specific temporary directory after container has been wiped out.
Also removing selinux label from process using --security-opt label=disable or running container using --privileged works as well.
I think that overall documentation on recommended SELinux attributes for various locations could be improved.
This issue is related to https://github.com/containers/podman.io/issues/373
I noticed there are still some long command-line options that are not shown correctly.
Instead of -- an – is shown.
It seems the character is called EN DASH:
https://charbase.com/2013-unicode-en-dash
The character EN DASH can be written with $'\u2013' in a Bash shell.
[esjolund@laptop ~]$ echo – | od
0000000 100342 005223
0000004
[esjolund@laptop ~]$ echo $'\u2013' | od
0000000 100342 005223
0000004
[esjolund@laptop ~]$
I'll use the $'\u2013' notation so that is clear what type of dash character is being used.
[esjolund@laptop ~]$ curl -s https://docs.podman.io/en/latest/markdown/podman-pod-rm.1.html | grep $'\u2013'
<p>podman pod rm –pod-id-file /path/to/id/file</p>
[esjolund@laptop ~]$
Let's use sed to replace the EN DASH character with the text string <ENDASH> so that any findings will be more visible:
[esjolund@laptop ~]$ curl -s https://docs.podman.io/en/latest/markdown/podman-pod-rm.1.html | grep $'\u2013' | sed $'s/\u2013/<ENDASH>/g'
<p>podman pod rm <ENDASH>pod-id-file /path/to/id/file</p>
[esjolund@laptop ~]$
I created an empty directory
[esjolund@laptop ~]$ mkdir /tmp/a
[esjolund@laptop ~]$ cd /tmp/a
and let the following command
wget -r https://docs.podman.io/en/latest/Commands.html
run for a while to download manual pages. I pressed Ctrl-C to terminate it.
[esjolund@laptop a]$ find . -type f -name '*.html' | wc -l
127
[esjolund@laptop a]$ grep --include '*.html' -r $'\u2013' . | wc -l
115
[esjolund@laptop a]$
The grep command found some more examples of the EN DASH character.
When running a container with a published port (rootless) like so:
podman run -dt -p 8080:80 docker.io/library/httpd:2.4
And restarting the container afterwards:
podman restart -l
One will get an error like:
Error: failed to expose ports via rootlessport: "listen tcp 0.0.0.0:8080: bind: address already in use\n"
and the container will be stopped. Starting the container via start afterwards works fine. A coredump will be created via systemd:
Mai 05 10:52:52 nb01 systemd-coredump[9161]: Process 9009 (exe) of user 1000 dumped core.
Stack trace of thread 9019:
#0 0x000055fc0cc93701 runtime.raise (podman + 0xb6d701)
#1 0x000055fc0cc779ae runtime.sigfwdgo (podman + 0xb519ae)
#2 0x000055fc0cc762e4 runtime.sigtrampgo (podman + 0xb502e4)
#3 0x000055fc0cc93a73 runtime.sigtramp (podman + 0xb6da73)
#4 0x00007f0c6728ca90 __restore_rt (libpthread.so.0 + 0x14a90)
#5 0x000055fc0cc93701 runtime.raise (podman + 0xb6d701)
#6 0x000055fc0cc7757a runtime.crash (podman + 0xb5157a)
#7 0x000055fc0cc607f6 runtime.fatalpanic (podman + 0xb3a7f6)
#8 0x000055fc0cc60191 runtime.gopanic (podman + 0xb3a191)
#9 0x000055fc0cc31b29 runtime.chansend (podman + 0xb0bb29)
#10 0x000055fc0cc31545 runtime.chansend1 (podman + 0xb0b545)
#11 0x000055fc0dba359f github.com/containers/libpod/pkg/rootlessport.parent.func1 (podman + 0x>
#12 0x000055fc0dba2ad8 github.com/containers/libpod/pkg/rootlessport.parent (podman + 0x1a7cad>
#13 0x000055fc0dba3418 github.com/containers/libpod/pkg/rootlessport.init.0.func1 (podman + 0x>
#14 0x000055fc0dee44ab main.main (podman + 0x1dbe4ab)
#15 0x000055fc0cc62c2a runtime.main (podman + 0xb3cc2a)
#16 0x000055fc0cc91b21 runtime.goexit (podman + 0xb6bb21)
-- Subject: Process 9009 (exe) dumped core
https://podman.io/ currently shows a 404.
and http://docs.podman.io/ is up but isn't using https
Am I supposed to install Docker before installing Podman?
Does Podman require Docker in order to run correctly?
I assumed that Podman could be installed without Docker, but if I just install Podman, then a lot of things don't work properly.
Coming from here I ended up on this page after clicking the link that was supposed to lead me to the man page for registries.conf.5, but the proper link appears to be this one instead (likely a rename of registries.conf.5.md to containers-registries.conf.5.md).
I didn't check whether similar issues exist for all URLs, though, but this is another instance from the same documentation page.
I had opened this (wrongly) over here. I'll provide a pull request hopefully sometime over the weekend.
Hi,
FYI I've found a dead link in the Posts of Interest section:
"hostnextra.com site - Easy to Install Podman on Ubuntu 20.04 - Like the title says, how to easily install Podman on Ubuntu 20.04."
https://github.com/containers/podman.io/blob/master/_posts/2020-12-07-podman-posts-of-interests.md
Thanks
https://github.com/containers/podman.io/blob/8b476d7e56d3563c71f5b884e2d339b624ab9d5e/index.html#L23
Shouldn't this have been alias docker="podman" instead?
so:
docker ps
would actually invoke:
podman ps
Ref: https://github.com/containers/podman.io/pull/67/files#r253282319
Hi!
I've received the following comment on Twitter:
https://twitter.com/bobschi/status/1262740627160064000?s=20
While for the tech. ppl. the explanation on podman.io is eventually fine, for non-tech. ppl., this might not be that obvious. Could the start page be reworked so it clearly points out the benefits in contrast to ?
Thanks,
Oliver
Why my system logs flooded with message container kill 8f3ff324c6a5188c9ff63ac3f870cc6c4ffc1a3046f4db025dc2d62f4de39f76 (image=dev-registry.sbis.ru/local_stand/inside:20.2100, name=inside) when I start container?
$ podman --version
podman version 1.8.1-dev
W: GPG error: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_20.04 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/testing/xUbuntu_20.04 InRelease' is not signed.
W: GPG error: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04 InRelease' is not signed.
Hi!
I'm following podman development with my feedreader and the URL's pointing to podman.io look like this most of the time:
<link href="https:/podman.io/feed.xml" rel="self" type="application/atom+xml" />Note the single / there after https:!
This makes the links from my feed reader not working correctly (I end up at https://podman.io/podman.io/new/2019/04/16/new.html) 😢
It would be ideal to have native mac and windows support to further the adoption of podman in the community. Users do not want to have a Linux VM just to use podman on these platforms. Furthermore, users won't read the entire README to find out that you really only support Linux and not Mac/Windows without a Linux VM.
When i try to pull any image from artifactory, I received the error:
ERRO[0001] error pulling image "registry:5000/base/base_alpine": unable to pull registry:5000/base/base_alpine: unable to pull image: Error initializing image from source docker://registry:5000/base/base_alpine: invalid character '<' looking for beginning of value
The same image pulled with Docker doesn't return this error and the result is succesful.
Does anyone have the same problem or a solution for this? Thanks.
The Getting Started page only has two links: installation instructions and getting-started/getting-started.
Moving the actual instructions to /getting-started would save people an extra click. Especially not needed since the first step on getting-started/getting-started is 'Install'
Seems like whatever (Jekyll?) is generating the RSS feed renders the newest post twice -- followed by the next x entries. Which leads to everything getting double entries as a feed reader continually refreshes it.
Here's a sample of the first two entries on the feed currently:
<entry>
<title type="html">Pulling podman images from a container repository</title>
<link href="https://podman.io/blogs/2020/03/31/build-pull-options.html" rel="alternate" type="text/html" title="Pulling podman images from a container repository"/>
<published>2020-03-31T00:00:00+00:00</published>
<updated>2020-03-31T00:00:00+00:00</updated>
<id>
https://podman.io/blogs/2020/03/31/build-pull-options
</id>
<content type="html" xml:base="https://podman.io/blogs/2020/03/31/build-pull-options.html">
<p><img src="https://podman.io/images/podman.svg" alt="podman logo" /></p> <h1 id="pulling-podman-images-from-a-container-repository">Pulling podman images from a container repository</h1> <h2 id="by-tom-sweeney-github-twitter">By Tom Sweeney <a href="https://github.com/TomSweeneyRedhat">GitHub</a> <a href="https://twitter.com/TSweeneyRedHat">Twitter</a></h2> <p>Tom Sweeney has another blog post on the <a href="https://www.redhat.com/sysadmin/">Red Hat Enable Sysadmin</a> site this time he’s writing about <a href="https://www.redhat.com/sysadmin/podman-image-pulling">Pulling podman images from a container repository</a>. Learn the different varities of pull that the <code class="language-plaintext highlighter-rouge">podman build</code> command can use to speed up or further secure your environment in this post.</p>
</content>
<author>
<name>tsweeney</name>
</author>
<category term="containers,"/>
<category term="images,"/>
<category term="docker,"/>
<category term="buildah,"/>
<category term="podman,"/>
<category term="hpc,"/>
<category term="oci,"/>
<category term="networking,"/>
<category term="runtime,"/>
<category term="windows,"/>
<category term="microsoft"/>
<summary type="html">
Pulling podman images from a container repository By Tom Sweeney GitHub Twitter Tom Sweeney has another blog post on the Red Hat Enable Sysadmin site this time he’s writing about Pulling podman images from a container repository. Learn the different varities of pull that the podman build command can use to speed up or further secure your environment in this post.
</summary>
</entry>
<entry>
<title type="html">Pulling podman images from a container repository</title>
<link href="https://podman.io/new/2020/03/31/new.html" rel="alternate" type="text/html" title="Pulling podman images from a container repository"/>
<published>2020-03-31T00:00:00+00:00</published>
<updated>2020-03-31T00:00:00+00:00</updated>
<id>https://podman.io/new/2020/03/31/new</id>
<content type="html" xml:base="https://podman.io/new/2020/03/31/new.html">
<p>Tom Sweeney has another blog post on the <a href="https://www.redhat.com/sysadmin/">Red Hat Enable Sysadmin</a> site this time he’s writing about <a href="https://www.redhat.com/sysadmin/podman-image-pulling">Pulling podman images from a container repository</a>. Learn the different varities of pull that the <code class="language-plaintext highlighter-rouge">podman build</code> command can use to speed up or further secure your environment in this post.</p>
</content>
<author>
<name>tsweeney</name>
</author>
<summary type="html">
Tom Sweeney has another blog post on the Red Hat Enable Sysadmin site this time he’s writing about Pulling podman images from a container repository. Learn the different varities of pull that the podman build command can use to speed up or further secure your environment in this post.
</summary>
</entry>
I think it would be nice to add a favicon to podman.io. Maybe the seals of the podman logo can be reused?
I seem to have found an interesting bug dealing with how the container networking is setup on system reboots. The container I am trying to run is created and launched by systemd and is enabled on restart.
Here is the service file for my container:
[Unit]
Description = Squid Proxy Container Service
Wants = network.target
[Service]
Restart = always
Type = simple
RemainAfterExit = yes
ExecStart = /usr/bin/podman run -dt -v /etc/squid/squid.conf:/etc/squid/squid.conf:Z -p 3128:3128 --name squid-cont squid-img
ExecStop = /usr/bin/podman stop -t 2 squid-cont
ExecStop = /usr/bin/podman rm squid-cont
[Install]
WantedBy = multi-user.target
Right off the bat, there is no way to reach the container externally on port 3128. Sending a ping to 1.1.1.1 from within the container results in the following when doing a tcpdump (note that this is listening on all interfaces):
[Interface:veth10d87c76:] 10:02:56.349301 IP 10.88.1.201 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
[Interface:cni0:] 10:02:56.349301 IP 10.88.1.201 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
[Interface:ens192:] 10:02:57.373370 IP 10.88.1.201 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
The ip address of my container is 10.88.1.201 and the host machine's ip is 10.11.4.34. As you can see, there must be some sort of NAT issue between the cni0 interface and the ens192 interface where the ip is not translated over.
The expected output from tcpdump if things were working properly would be like this:
[Interface:veth10d87c76:] 10:02:56.349301 IP 10.88.1.201 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
[Interface:cni0:] 10:02:56.349301 IP 10.88.1.201 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
[Interface:ens192:] 10:02:57.373370 IP 10.11.4.34 > 1.1.1.1: ICMP echo request, id 54, seq 1, length 64
To further complicate things, restarting the service will resolve the problem and the ip translation between the interfaces works as expected. Additionally, bringing up another container manually will resolve the issue. The only time I am seeing this problem is when the container is launched as a service on startup after rebooting the system.
The docker docs https://docs.docker.com/engine/reference/commandline/cp/ say that when copying and the SRC_PATH ends with "/." and the DEST_PATH is a directory that it will copy the contents of SRC_PATH to DEST_PATH.
Podman is copying the SRC_PATH to DEST_PATH and not the contents of SRC_PATH.
For example I do:
$ podman cp --pause=false gracious_goodall:/root/. ~/output/
$ ls ~/output/
root
Which is not working as the 'docker cp' documentation says it should be. It should copy the "contents" of the /root/ directory and not the directory (including the directory name).
Following link is broken on this page (https://podman.io/getting-started/installation) is broken.
Remote Client
Latest remote client for MacOS (https://storage.googleapis.com/libpod-master-releases/podman-remote-latest-master-darwin-amd64.zip)
it would be great if you can fix the link and provide some detailed steps to setup podman on OSX. Thank you!
I have to actually scroll vertically to see the actual content which is bad design. This goes against every best practice.
So much wasted space:
The other issues are that your website should be self-contained...don't' link to the github markdown files, host them on the website. You folks could benefit from Google Season of Docs.
I know my limits and frontend design is not my thing, but I do have proposals to fix it:
Use bootstrap or another CSS framework to get responsiveness easy, or use a jekyll template that is known to work. Going the way you did is not good. I do not want to have people writing off podman because the website design isn't great. That more or less happened with me -- but fixing the design can make this turnaround.
The paragraph in https://github.com/containers/podman.io/blob/master/getting-started/index.md#testing-the-httpd-server starts with "Now that we have the IP address of the container". But in the previous paragraph it is pointed out, that there is no IP address.
Hey 👋,
Just saw that we add the podman logo for each blog post which looks a bit noisy from my perspective:
Do you think we could remove them and stick to a single logo on top?
been on your website - distinct lack of explaining what podman is and what problem it solves
"What is Podman? Simply put: alias docker=podman"
my #2 pet peeve after poor setup instructions
thanks!
Someone linked to www.podman.io, and it results in a bad certificate warning from the browser.
I want to know do podman compatible with gvisor . Being OCI and runsc , I believe it should, but just need confirmation.
Sorry, If it is a dumb question.
https://gvisor.dev/
gVisor is an application kernel, written in Go, that implements a substantial portion of the Linux system surface. It includes an Open Container Initiative (OCI) runtime called runsc that provides an isolation boundary between the application and the host kernel.
I get a baseurl starting with http://
$ curl -s https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/devel:kubic:libcontainers:stable.repo | grep baseurl
baseurl=http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/
$
I would have expected a baseurl starting with https://
$ curl -s https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/devel:kubic:libcontainers:stable.repo | grep baseurl
baseurl=https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/
$
Hey,
It would be great if you could add in the installation instructions for "RHEL8 Beta", that the module container-tools:1.0 is the stable stream version, and that there is also a "fast stream version" (container-tools:rhel8) available to have more recent version of the tools.
As the stable stream has pretty old tools (podman-1.0.2), some users might want to use the fast stream.
Would be nice to forward http to https for docs.podman.io
My understanding is that the important features of Podman, in isolation, are:
(Maybe I'm wrong!) But if you don't already know what Podman is, https://podman.io/ is surprisingly little help. It has this to say:
Manage pods, containers, and container images.
What is Podman? Simply put:
alias docker=podman
This may be true, but it doesn't explain why you would want to use podman rather than Docker.
If you drill down into https://podman.io/releases/ we get a bit closer (emphasis mine):
Our original goal with Podman was to provide a fully-featured debugging experience for CRI-O, but it has become so much more. Podman 1.0.0 is a fully-featured container engine. It provides a Docker-compatible command line to ease the transition from other container engines. Most Podman commands can be run as a regular user, without requiring additional privileges. Furthermore, all of this is accomplished without a daemon!
https://github.com/containers/libpod#readme is also linked, and from there you can get to
https://github.com/containers/buildah/tree/master/docs/containertools#readme which is also a bit more informative. It would be nice if the front page of the website included some of this information.
Hi all,
I am currently working on my own blog and therefore started a podman series. I have seen some cross posts from "Enable Sysadmin". Is it possible (in general) to cross post blogs from the below?
Is there any guideline / best practice for the same?
The "Out of scope" section of the "what is Podman?" page, which is referenced on the main page, is outdated. It still contains a whole paragraph about why Podman won't support docker-compose, but it's been supported since Podman 3.0.
On the web page
http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html
there is the text
–name, -n
I would have expected to see two hyphens before name, i.e.
--name, -n
I think the same problem is present for all long command-line options and on all man pages.
I guess this is related to how the man pages are generated from the source code.
(Unfortunately I don't know about how that works)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.