-
Notifications
You must be signed in to change notification settings - Fork 144
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
Support container provisioner in toolbox #3228
Conversation
@jkonecny12 this is the change I talked about, with it tmt container provisioner works well :) |
I'm getting this error, any idea? The directory
|
@janhavlin this is something we should document, add this to your environment (I have it in .bashrc):
|
Thanks, I got it working! |
Couldn't we have this resolved by default correctly? Requesting users to set somewhere something to make things work seems like an issue generator and unhappy users. |
@jkonecny12 I agree it is sad, but we will need to have a discussion with |
So we agreed we will go with this default if we detect running in toolbox :) |
ce8a3c6
to
2579e3c
Compare
FTR the workdir autodetection will be another patch but it won't be in 1.40. |
2579e3c
to
3a12526
Compare
a2df6da
to
e58860d
Compare
e58860d
to
a2f97ba
Compare
8944e90
to
34d2311
Compare
34d2311
to
8664605
Compare
For Fedora Silverblue users it is common to run podman via `flatpak-spawn --host` which runs podman on the host system itself. This requires to pass the toolbox container name when running `podman cp` to correctly copy stuff from the toolbox container, where `tmt` is installed to the provisioned container. Fixes #1020 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
4121741
to
ed8281a
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.
The change itself looks good. The test setup looks really super-complex and thus, I'm afraid, a bit fragile. Added a few comments though.
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
I simplified, so I hope this concern is now addressed |
/packit build |
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.
Looks much better now, thanks! Though it seems that tests are red. You've mentioned that el9
should be disabled, right? Plus there's seems to be an avc failure on fedora-41+
.
6f30463
to
9c96137
Compare
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
yes, disabling avc check and centos stream 9, I tried to make it work, but it is a mess |
/packit build |
Issues here are unrelated, merging |
For Fedora Silverblue users it is common to run podman via `flatpak-spawn --host` which runs podman on the host system itself. This requires to pass the toolbox container name when running `podman cp` to correctly copy stuff from the toolbox container, where `tmt` is installed to the provisioned container. Fixes #1020 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
For Fedora Silverblue users it is common to run podman via
flatpak-spawn --host
which runs podman on the host system itself. This requires to pass the toolbox container name when runningpodman cp
to correctly copy stuff from the toolbox container, wheretmt
is installed to the provisioned container.Fixes #1020
Pull Request Checklist