From: Andersen, John <john.s.andersen at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-abrmd in a container
Date: Mon, 04 Feb 2019 10:08:09 -0800 [thread overview]
Message-ID: <20190204180809.GA17746@johnsa1-desk.jf.intel.com> (raw)
In-Reply-To: CAKrSGQS_pe=U-staHmcyoRYgYofSTexkxSC=sYem=K1r=P9Wcg@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]
On Mon, Feb 04, 2019 at 04:57:12PM +0000, Luke Hinds wrote:
> On Mon, Feb 4, 2019 at 4:12 PM Roberts, William C
> <[1]william.c.roberts(a)intel.com> wrote:
>
> 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.
>
> Do you mean the following travis-ci file:
> [2]https://github.com/tpm2-software/tpm2-abrmd/blob/master/.travis.yml#
> L2
> I noticed this, but I think its a VM (unless I am mistaken):
> [3]https://docs.travis-ci.com/user/reference/overview/#virtualization-e
> nvironments
> Any pointers to files that reference your container use, would be
> helpful.
> Cheers,
> Luke
>
> > -----Original Message-----
> > From: tpm2 [mailto:[4]tpm2-bounces(a)lists.01.org] On Behalf Of Luke
> Hinds
> > Sent: Monday, February 4, 2019 7:47 AM
> > To: [5]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
>
> --
> Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
> e: [6]lhinds(a)redhat.com | irc: lhinds @freenode | t: +44 12 52 36 2483
>
> References
>
> 1. mailto:william.c.roberts(a)intel.com
> 2. https://github.com/tpm2-software/tpm2-abrmd/blob/master/.travis.yml#L2
> 3. https://docs.travis-ci.com/user/reference/overview/#virtualization-environments
> 4. mailto:tpm2-bounces(a)lists.01.org
> 5. mailto:tpm2(a)lists.01.org
> 6. mailto:lhinds(a)redhat.com
Some dbus stuff happened in the tools repo recently. Not sure if this would be
of help.
https://github.com/tpm2-software/tpm2-tools/commit/9a6430ef293bc1a506224431af9370c7748f39b4
> _______________________________________________
> tpm2 mailing list
> tpm2(a)lists.01.org
> https://lists.01.org/mailman/listinfo/tpm2
next reply other threads:[~2019-02-04 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:08 Andersen, John [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 16:57 Luke Hinds
2019-02-04 16:11 Roberts, William C
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=20190204180809.GA17746@johnsa1-desk.jf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox