-
Notifications
You must be signed in to change notification settings - Fork 25
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
Packit: initial enablement #2
Conversation
/packit copr-build |
@rhatdan looks like
|
97f12ad
to
4acafd4
Compare
0acb018
to
267bb25
Compare
qm-selinux.spec.rpkg
Outdated
%dir %{_sharedstatedir}/qm/rootfs%{_datadir}/containers | ||
%{_sharedstatedir}/qm/rootfs%{_datadir}/containers/container_contexts | ||
%dir %{_libexecdir}/%{name} | ||
%{_libexecdir}/%{name}/install.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhatdan added the install.sh script to /usr/libexec/qm-selinux
. Please verify the change and remind me what else I need to add.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should name this /usr/libexec/qm-install
I am thinking of renaming this repo to just qm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should name this /usr/libexec/qm-install
I think the script should be 1 level further down. So, inside /usr/libexec/qm/
or if it's only to be used in conjunction with podman, maybe in /usr/libexec/podman/
.
I am thinking of renaming this repo to just qm
Dunno, I guess having the -selinux
in the name provides a better idea, but not a stong opinion. We could check with the team if you prefer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, /usr/libexec/qm/install would be good.
Or /usr/lib/qm/install since this is not to be executed by other users of a tool.
As far as the -selinux drop is concerned, the goal of this repo is setting up a QM isolated environment. The SELinux component is just a small part of it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, /usr/libexec/qm/install would be good. Or /usr/lib/qm/install since this is not to be executed by other users of a tool.
As far as the -selinux drop is concerned, the goal of this repo is setting up a QM isolated environment. The SELinux component is just a small part of it.
SGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
file path changed. PTAL
This commit adds Packit configuration files which will trigger builds on copr:`rhcontainerbot/packit-builds` on every PR and on copr:`rhcontainerbot/podman-next` on every commit to main branch. Signed-off-by: Lokesh Mandvekar <[email protected]>
@rhatdan also added qm.container to Could you please also remind me of the exact rpm testing steps? Right now I have:
|
Ok I the setup script needs to be modified to expect that the qm-selinux package was already built. |
@rhatdan ping, just checking if you've updated the script. |
I have not completed it yet, hopefully I will get back to this tomorrow. |
Ok I am going to merge, and then we can continue working and improving this. |
This commit adds Packit configuration files which will trigger builds on
copr:
rhcontainerbot/packit-builds
on every PR and oncopr:
rhcontainerbot/podman-next
on every commit to main branch.Signed-off-by: Lokesh Mandvekar [email protected]