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 1820551 - Automatically starting a container on boot is not possible through cockpit WebUI
Summary: Automatically starting a container on boot is not possible through cockpit WebUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-podman
Version: 8.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Matej Marušák
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-03 10:42 UTC by Apurbita Mukherjee
Modified: 2022-11-08 09:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:14:53 UTC
Type: Enhancement
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:15:31 UTC

Description Apurbita Mukherjee 2020-04-03 10:42:27 UTC 
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Build Identifier: 

Automatically starting a container on boot is not possible through cockpit WebUI.
Currently only it is possible to start a container, not have it automatically started on boot.

Reproducible: Always

Steps to Reproduce:
1. Have cockpit-podman installed and running
2. Download an image
3. Create a running container from that image

Actual Results:  
No option "start on boot"

Expected Results:  
Option "start on boot"



None.
Comment 1 Martin Pitt 2020-04-03 12:48:55 UTC 
I suppose we could integrate `podman generate systemd` to enable auto-start. I'm not a big fan of its start/stop approach instead of just killing/starting the container (that falls over too much), but at least from cockpit-podman's POV that's the official API. It has a convention for predictable unit names, so that we can also map a container to a unit name to see if autostart is enabled.
Comment 2 Derrick Ornelas 2020-04-06 16:14:04 UTC 
If it helps, we now document deleting/running (what I assume you mean by killing/starting) the container instead of start/stop.  

  https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/using-systemd-with-containers_building-running-and-managing-containers#starting_containers_with_systemd
  https://www.redhat.com/sysadmin/podman-shareable-systemd-services


I don't know the status of support for this in 'podman generate systemd', though.
Comment 3 Martin Pitt 2020-04-09 13:12:58 UTC 
Matej, want to have a look at that one?
Comment 5 Matej Marušák 2022-05-24 12:43:59 UTC 
This has been introduced in version cockpit-podman-39. It is only supported for superuser for now. Enabling it for normal user might come in future.
See release note: https://cockpit-project.org/blog/cockpit-260.html
Comment 8 Matej Marušák 2022-08-19 08:09:50 UTC 
This now also has support for normal users, see https://github.com/cockpit-project/cockpit-podman/pull/1039
Comment 14 errata-xmlrpc 2022-11-08 09:14:53 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-2022:7457
Note You need to log in before you can comment on or make changes to this bug.