From: Roberts, William C <william.c.roberts at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-abrmd in a container
Date: Mon, 04 Feb 2019 16:11:32 +0000 [thread overview]
Message-ID: <476DC76E7D1DF2438D32BFADF679FC5649CDE780@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: CAKrSGQQj4SSifdM78ELkw0LtoZbE1MEJ888EC0Ld_xK7D9gdjw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
I run it in our CI system which is using a docker container, not sure if that helps
But you can look at our scripts for it.
> -----Original Message-----
> From: tpm2 [mailto:tpm2-bounces(a)lists.01.org] On Behalf Of Luke Hinds
> Sent: Monday, February 4, 2019 7:47 AM
> To: tpm2(a)lists.01.org
> Subject: [tpm2] tpm2-abrmd in a container
>
> Hello,
>
> I have been working on trying to get tpm2-abrmd running in a container, but its
> proving problematic as there is a requirement on system-d and dbus. This in turn
> requires running the container as privileged and mounting the hosts cgroup (and
> adding cap sys-admin).
>
> My reason for using a container, is for CI / functional testing of a project that will
> use abrmd and having a lightweight means to test against the resource manager
> running in a container.
>
> I am still early in looking at ways to achieve this, so I wanted to ask if any others
> have snippets of previous attempts (successful or not) they could share?
>
> Thanks,
>
> Luke
next reply other threads:[~2019-02-04 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 16:11 Roberts, William C [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-06 7:50 [tpm2] tpm2-abrmd in a container Luke Hinds
2019-02-06 0:43 Javier Martinez Canillas
2019-02-05 15:40 Luke Hinds
2019-02-04 18:55 Luke Hinds
2019-02-04 18:08 Andersen, John
2019-02-04 16:57 Luke Hinds
2019-02-04 15:46 Luke Hinds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476DC76E7D1DF2438D32BFADF679FC5649CDE780@ORSMSX101.amr.corp.intel.com \
--to=tpm2@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.