-
Notifications
You must be signed in to change notification settings - Fork 26
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
fix e2e #231
fix e2e #231
Conversation
Now i see the whole install under rootfs is not working, @rhatdan @dougsland can you advise? is related to exploded container and podman-build? PS. still checking this
Will update PR |
aede9dc
to
94c74a1
Compare
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.
In general LGTM, @Yarboa have few questions
Resolves containers#226 Systemd is not installed under /usr/lib/qm/rootfs during create_qm container qm is failing since no /sbin/init created under /usr/lib/qm/rootfs adding cap-add SYS_ADMIN capability for build of nodeX Signed-off-by: Yariv Rachmani <yrachman@redhat.com>
94c74a1
to
04af9ef
Compare
|
04af9ef
to
6d91fb7
Compare
@dougsland @dennisbrendel |
Signed-off-by: Yariv Rachmani <yrachman@redhat.com>
6d91fb7
to
d31b816
Compare
thanks @Yarboa great fix |
Resolves #226
Systemd is not installed under /usr/lib/qm/rootfs
during
qm.service is failing since no /sbin/init created under /usr/lib/qm/rootfs once container is running
Adding w/a after nodeX container is up, to install systemd under rootfs