-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS installer pkg fails with command-line install #17910
Comments
Likely caused by #17786. For the unexpected root user I am not so sure, the auto install was added in #16565 |
yes if helper is already installed it should just continue |
maybe we should change it to always try to uninstall first with edit: |
Please see #17916 for a potential fix. |
Make sure we can install podman even when the podman-mac-helper install command fails. This used to be the behavior but commit bae07b6 caused the regression because the binary now returns 1 as exit code on errors. [NO NEW TESTS NEEDED] I am not sure if we can test the install step in CI. Fixes containers#17910 Signed-off-by: Paul Holzinger <[email protected]>
If I completely remove podman (sudo rm -rf /opt/podman) and restart, and then attempt (as root) to install podman,
Snippet from /var/log/install.log:
This is
Would you like this opened as a separate issue, or are you happy with just ignoring the error as you do here: #17916 |
you need to run it with sudo AFAICT so it can get your user id from the sudo env vars |
That's not helpful in a mass-deployment scenario. Software is not installed interactively by users -- we have a software distribution tool that runs as root. (In our case, we use Munki, but this would be the case with any software management tool: Jamf, Addigy, VMware Workspace ONE, SimpleMDM, FileWave, etc, or even configuration management tools like Ansible, Puppet, Chef, or SaltStack) |
Make sure we can install podman even when the podman-mac-helper install command fails. This used to be the behavior but commit bae07b6 caused the regression because the binary now returns 1 as exit code on errors. [NO NEW TESTS NEEDED] I am not sure if we can test the install step in CI. Fixes containers#17910 Signed-off-by: Paul Holzinger <[email protected]>
will it be included in an 4.4.4 or an updated 4.4.3 .PKG packages ? |
I'd really hope it would be in a 4.4.4 release, or a 4.4.3.x release. It's difficult to manage/track packages that are different, but have the same version number. |
see the discussion on the PR, goal is to create a 4.4.4 version |
Still having this issue in 4.5.1. |
@LtCmdrScott The install process needs to know the user to install the command with, so if it cant determine this it will fail. "Getting Error: unexpected root user" can happen if the user running the sudo command was root, and SUDO_USER wasn't defined (normally defined by sudo to the calling user [or mirrored to allow nesting]). One way this can occur is if the environment was dropped via some other nested call to other user invoking tools (e.g. su ). |
So I did this in my script:
and I am still getting "Error: unexpected root user". What did I miss? This is being run as a post install script from JAMF...When installing this software, I must install everything during installation as the users doesn't have admin rights to do this afterwards... |
Issue Description
TL; DR: attempts to upgrade Podman by installing the current release package on macOS fail.
Attempting to install the amd64-4.4.3 package for macOS from the command line fails, when run as root, or via sudo:
The issue is in the postinstall script:
Specifically,
/opt/podman/bin/podman-mac-helper install
. This tool fails a variety of ways. First: if an older version of Podman is already installed:Instead of failing, it should either upgrade the tool, or do the uninstall/install dance. But just failing the entire install seems like a bad idea.
I've also seen it fail with
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
Successful install
podman info output
podman 4.4.3, macOS, amd64 (x86_64)
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: