Actions
Support #34
open
What's the right way to launch "dnf install..." from within a non-root binding ?
Start date:
11/23/2022
Due date:
% Done:
0%
Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.0
OS Fix Version/s:
Labels:
Description
In order to perform a system update my binding needs to launch dnf install....
But dnf can only be launched by user root, whereas my binding is at the moment started as user rp-owner like shown below:
BMS2ORP_BINDING=bms2orp-binding
RP_USER=rp-owner
AFM_CMD="runuser -u ${RP_USER} -- afm-util"
${AFM_CMD} start ${BMS2ORP_BINDING} > /dev/null
Please detail how this problem can be solved within redpesk framework.
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- Assignee changed from Vincent Rubiolo to José Bollo
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- OS Affects Version/s arz-1.0 added
- OS Affects Version/s deleted (
arz-1.0.0)
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- Target version changed from arz-1.0-update to arz-1.0.2
Updated by José Bollo about 1 year ago
- Status changed from New to Submitter feedback needed
newer version of the spawn-binding are currently evaluated.
We need to get more detail on the need:
- is it "dnf install a-predefined-application"?
- is it "dnf install a-parametric-application"?
- is it also "dnf update/upgrade"?
Updated by Emmanuel Jubera [SAFT] about 1 year ago
Hello Jose,
The idea was to have spawn-binding launching a shell script that would run dnf to install a few rpms.
The list of rpms can vary but support for "dnf update/upgrade" isn't required.
Emmanuel.
Updated by Emmanuel Jubera [SAFT] 5 months ago
- Priority changed from High to Normal
Priority decreased to normal as a workaround was developed to allow installation of rpms with dnf.
Updated by Sebastien Douheret [IoT.bzh] 3 months ago
- Target version changed from arz-1.0.2 to arz-1.1-update
Actions