1837755 – --init feature useless out of the box

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1837755 - --init feature useless out of the box

Summary: --init feature useless out of the box

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	podman
Sub Component:
Version:	---
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	8.3
Assignee:	Jindrich Novy
QA Contact:	atomic-bugs@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1186913 1804543
TreeView+	depends on / blocked

Reported:	2020-05-19 22:08 UTC by Bill Nottingham
Modified:	2023-10-06 20:08 UTC (History)
CC List:	16 users (show)
Fixed In Version:	podman 2.0.2-2 and newer
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-11-04 03:05:17 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Bill Nottingham 2020-05-19 22:08:13 UTC

Description of problem:

[cloud-user@rhel8-base ~]$ podman run --init memcached:alpine sh
Trying to pull registry.access.redhat.com/memcached:alpine...
  name unknown: Repo not found
...
Trying to pull docker.io/library/memcached:alpine...
Getting image source signatures
...
Storing signatures
Error: container-init binary not found on the host: stat /usr/libexec/podman/catatonit: no such file or directory
[cloud-user@rhel8-base ~]$ sudo dnf list \*catatonit\*
Updating Subscription Management repositories.
Last metadata expiration check: 0:01:23 ago on Tue 19 May 2020 06:04:38 PM EDT.
Error: No matching Packages to list
[cloud-user@rhel8-base ~]$ sudo dnf install /usr/libexec/podman/catatonit
Updating Subscription Management repositories.
Last metadata expiration check: 0:01:35 ago on Tue 19 May 2020 06:04:38 PM EDT.
No match for argument: /usr/libexec/podman/catatonit
Error: Unable to find a match: /usr/libexec/podman/catatonit

Version-Release number of selected component (if applicable):

podman-1.6.4-11.module+el8.2.0+6368+cf16aa14.x86_64

How reproducible:

100%

Steps to Reproduce:
1. see docker --init
2. google for podman replacement
3. find https://github.com/containers/libpod/pull/2045
4. try to use it

Actual results:

<sad trombone>

Additional info:

Guess we'll keep bundling tini in our images.

Comment 2 Colin Walters 2020-05-19 22:34:02 UTC

xref https://github.com/coreos/coreos-assembler/pull/1451#issuecomment-628194485

Comment 3 Matthew Heon 2020-05-20 13:48:01 UTC

Two potential approaches here:
1. If there is another init-type binary available in the repos (`tini` for example) we can swap the config files to point to that. I'm not optimistic about this being the case
2. We try and get catatoinit packaged for the next reasonable RHEL release (8.3, maybe) and ship it there, but ensuring the init we want to use is available (We could also package another init, but if we're already going through the trouble, might as well grab the one we wanted to use).

I know there were significant holdups getting katatoinit into Fedora, but AFAIK those have been resolved now.

Going to reassign to Jindrich as this one seems like a packaging issue.

Comment 4 Jindrich Novy 2020-05-20 14:29:32 UTC

catatonit has only been recently added to Fedora. Time to add it to container-tools Scott, Dan, Valentin?

Comment 5 Valentin Rothberg 2020-05-20 14:36:12 UTC

Sounds good to me, but let's wait for Scott and Dan

Comment 6 Bill Nottingham 2020-05-20 15:49:42 UTC

From an end-user perspective, I don't care as much about which mini init it is, just that whatever podman's default is is actually there. (ideally, Required:, not just Recommended:)

Comment 7 Scott McCarty 2020-05-20 16:01:13 UTC

I'll defer to Dan as I only have a vague notion of the purpose of this feature. Here's a dumb question - why wouldn't "podman run --init" not just use systemd? (for some reason, I feel like people might throw heavy things at me) :-)

Comment 8 Matthew Heon 2020-05-20 16:18:03 UTC

We need to be able to mount the init into the container (ideally in an image-agnostic way, to support scratch images). If we had a static-linked systemd that would be doable, but that doesn't appear to be a configuration we ship.

Comment 9 Daniel Walsh 2020-05-20 16:43:34 UTC

Yes this feature is not something we recommend, but it is needed to match Docker CLI.
We should just ship this small init program and make it Required

Comment 10 Jindrich Novy 2020-06-05 17:23:13 UTC

Assigning to Matt based on comment #8.

Matt, let me know if anything needs to be done on packaging side after it's done.

Thanks.

Comment 23 Alex Jia 2020-08-25 16:29:34 UTC

I can reproduce this bug on podman-1.6.4-10.module+el8.2.0+6063+e761893a.x86_64,
and it works on podman-2.0.2-2.module+el8.3.0+7374+9d949f97 and
podman-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64


[root@hpe-dl380pgen8-02-vm-15 ~]# rpm -q podman podman-catatonit
podman-2.0.2-2.module+el8.3.0+7374+9d949f97.x86_64
podman-catatonit-2.0.2-2.module+el8.3.0+7374+9d949f97.x86_64

[root@hpe-dl380pgen8-02-vm-15 ~]# podman run --init memcached:alpine sh
...ignore...
Trying to pull docker.io/library/memcached:alpine...
Getting image source signatures
Copying blob a01e9fc6969f done
Copying blob 469ce346395c done
Copying blob a644683dc78e done
Copying blob 9da9e0d7f928 done
Copying blob df20fa9351a1 done
Copying blob ee44cd26437f done
Copying config 6c8afc725f done
Writing manifest to image destination
Storing signatures

[root@hpe-dl380pgen8-02-vm-15 ~]# podman ps -a
CONTAINER ID  IMAGE                               COMMAND  CREATED         STATUS                     PORTS   NAMES
0c6056d0bbbe  docker.io/library/memcached:alpine  sh       22 seconds ago  Exited (0) 22 seconds ago          confident_morse

[root@hpe-dl380pgen8-02-vm-15 ~]# rpm -q podman podman-catatonit
podman-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64
podman-catatonit-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64

[root@hpe-dl380pgen8-02-vm-15 ~]# podman run --init memcached:alpine sh
Trying to pull registry.access.redhat.com/memcached:alpine...
...ignore...
Trying to pull docker.io/library/memcached:alpine...
Getting image source signatures
Copying blob 469ce346395c done
Copying blob ee44cd26437f done
Copying blob df20fa9351a1 done
Copying blob 9da9e0d7f928 done
Copying blob a644683dc78e done
Copying blob a01e9fc6969f done
Copying config 6c8afc725f done
Writing manifest to image destination
Storing signatures

[root@hpe-dl380pgen8-02-vm-15 ~]# podman ps -a
CONTAINER ID  IMAGE                               COMMAND  CREATED         STATUS                     PORTS   NAMES
12111a13868e  docker.io/library/memcached:alpine  sh       12 seconds ago  Exited (0) 11 seconds ago          dazzling_chaplygin

Comment 26 errata-xmlrpc 2020-11-04 03:05:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4694

Note You need to log in before you can comment on or make changes to this bug.