Skip to content
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

Also substitute $HOME in runlabel with user's homedir #22529

Merged

Conversation

dcermak
Copy link
Contributor

@dcermak dcermak commented Apr 29, 2024

Some programs have their configuration files relative to the user's home. It would be convenient being able to mount these into the container, but that requires expansion of ~ or $HOME in a label. This commit adds support for that for the runlabel command.

Does this PR introduce a user-facing change?

- expand `$HOME` in labels when called via the `runlabel` command

Copy link

Ephemeral COPR build failed. @containers/packit-build please check.

@lsm5
Copy link
Member

lsm5 commented Apr 29, 2024

ignore el9 failures

Copy link
Member

@edsantiago edsantiago left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your PR! Two suggestions inline, subject to override by our more Go-literate team members.

pkg/domain/infra/abi/containers_runlabel.go Outdated Show resolved Hide resolved
pkg/domain/infra/abi/containers_runlabel.go Outdated Show resolved Hide resolved
@dcermak dcermak force-pushed the substitute-home-in-runlabel branch from b15e15f to 437628c Compare April 29, 2024 14:19
Some programs have their configuration files relative to the user's
home. It would be convenient being able to mount these into the container, but
that requires expansion of `~` or `$HOME` in a label. This commit adds support
for that for the `runlabel` command.

Signed-off-by: Dan Čermák <dcermak@suse.com>
@dcermak dcermak force-pushed the substitute-home-in-runlabel branch from 437628c to 46f247d Compare May 3, 2024 12:00
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 3, 2024
Copy link
Contributor

openshift-ci bot commented May 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcermak, Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 3, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f1b8439 into containers:main May 6, 2024
90 of 91 checks passed
@dcermak dcermak deleted the substitute-home-in-runlabel branch May 6, 2024 16:16
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 5, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Aug 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants