-
Notifications
You must be signed in to change notification settings - Fork 19
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
Test upsteam container images #429
Conversation
d41e660
to
8375ac2
Compare
I am wondering what's behind those test failure, seems like there was an issue with agent start. Unfortunately, logging for containers is not currently ideal. EDIT: seems there is in fact something in logs
|
I already fixed this locally. For images that already have an entrypoint set, you need to override it, otherwise the trailing commands are provided as arguments. But I hit another issue: the upstream agent container image does not create an internal I think it is better to add the |
b3bbb62
to
1ec2ec1
Compare
Added the |
62f6ffa
to
959f93e
Compare
4c159b9
to
00e0032
Compare
container/functional/keylime_ipv6_multihost/payload-script/local_action_modify_payload.sh
Fixed
Show fixed
Hide fixed
container/functional/keylime_ipv6_multihost/payload-script/local_action_modify_payload.sh
Fixed
Show fixed
Hide fixed
container/functional/keylime_ipv6_multihost/payload-script/local_action_modify_payload.sh
Fixed
Show fixed
Hide fixed
97d014d
to
5c48481
Compare
bcec874
to
5ba47f5
Compare
/packit retest |
I am trying to address C9S failure in #450. |
@@ -8,6 +8,8 @@ | |||
|
|||
[ -n "$AGENT_DOCKERFILE" ] || AGENT_DOCKERFILE=Dockerfile.upstream.c9s | |||
|
|||
[ -n "$REGISTRY" ] || REGISTRY=quay.io |
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.
Should we make images configurable through envvars as well?
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.
Now I can see we do configure it through envvars, it's just not clearly visible in the test. What about adding a comment to the top?
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'll try to make it clear.
container/functional/keylime_ipv6_multihost/payload-script/local_action_modify_payload.sh
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.
Thank you for the update. Looks good, I would just consider adding a comment to a test mentioning which images can be defined using envvars from the outside.
@Koncpa please take a look at it as it introduces some new functions and concepts. |
Sure, I'll take a look. |
This makes it possible to run using the same command line regardless of the image having an entrypoint set or not. Also, allow passing arguments to the command inside the container Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
The helper function limeconPullImage will pull an image from a remote registry and optionally tag it with a name and tag locally. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Just one nitpick, but otherwise LGTM! Thank you. |
Enable container tests to run against images obtained from registries instead of built locally. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Modify containers test plan to test using images from upstream registry for the verifier, registrar, and agent. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
If a Dockerfile for any component is provided via environment variable, check if it exists and, only if not found, try to find in limeLibraryDir. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Use --entrypoint to override the image entrypoint in case it has an entrypoint set. The agent needs the certificate directory to be accessible by the internal 'keylime' user in order to drop privileges inside the container. For this, it is necessary for the files owner uid to match the internal 'keylime' uid. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
The agent will store data in /var/lib/keylime which needs to be accessible by the unprivileged user in the container. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Replace the python payload action with a shell payload action to avoid the need for python inside the agent container. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Use a separate container for the revocation webhook. Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
Signed-off-by: Anderson Toshiyuki Sasaki <[email protected]>
--entrypoint
to override the container entrypoint and allow passing arguments to the commands inside the container inlimeconRun
limeconRunAgent
keylime_ipv6_multihost
testkeylime_ipv6_multihost
by replacing python payload script with shell script