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
containers: some tests always succeed #21044
Comments
So we need a test to check that the nixos-container tool works as expected? Wouldn't it be kind of better to revert c37e76b until upstream fixes that? |
I think switching to |
@wlhlm Thanks a lot for the hint! If nobody else wants to take a shot at it I'll try to implement and test this in the next few days. |
(triage) systemd/systemd#4215 has now been closed without (as far as I understand) the behavior of systemd being changed. Does someone know what was once a reproducer to check whether it's still an issue? I don't personally use |
As suggested by @wlhlm, I will close this issue as it is not relevant anymore |
Since c37e76b
machinectl shell
is used to run commands inside containers instead ofnsenter + su
. Howevermachinectl shell
does not forward the return code of the command to the caller (see systemd/systemd#4215) so all the tests that usenixos-container run
always succeed (e.g container-physical_interfaces.nix). So as long as systemd/systemd#4215 is not solved some tests may succeed when in fact they should have failed.The text was updated successfully, but these errors were encountered: