-
Notifications
You must be signed in to change notification settings - Fork 9
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
e2e: run regression tests on bare metal #907
Conversation
- platform: | ||
self-hosted: true |
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'm surprised that this works, I always assumed it wouldn't.
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.
You mean the partial matching of objects? I did not know either - could be better documented, I guess.
...ges/by-name/kata/kata-runtime/0014-tools-don-t-clean-build-root-when-generating-rootfs.patch
Outdated
Show resolved
Hide resolved
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.
LGTM :)
79302d5
to
e92318c
Compare
Ensure that known test cases work, regardless of platform, and fix a couple of issues for the tests to succeeded:
MongoDB
MySQL
The MySQL images need additional configuration to run, otherwise they end up crash-looping and cause sporadic errors.
Varnish
The Varnish we're using is a source-to-image image which does not actually run a server in the default configuration. Since I don't know how we would want to configure Varnish in the first place, I'm removing the image. cc @miampf
Image build
The
CONFIDENTIAL_GUEST
environment variable for the rootfs build is set upstream when COCO guest components are provided. Since we don't provide them, we need to set it manually so that we get the features enabled by it.For now, the only feature guarded by this variable is an increased
/run
mount size. However, there seems to be a bug in the implementation, because the systemd target that's edited is not yet in the new root, sosystemd-remount-fs
is not enabled and thus modifyingfstab
has no effect. We work around this by adding the targets before the rootfs build and disabling a cleanup step in the build script.