From: Andersen, John <john.s.andersen at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Docker Images
Date: Wed, 28 Aug 2019 14:05:12 -0700 [thread overview]
Message-ID: <20190828210511.GF14525@johnsa1-desk.jf.intel.com> (raw)
In-Reply-To: 476DC76E7D1DF2438D32BFADF679FC5649DEF841@ORSMSX101.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Wed, Aug 28, 2019 at 08:19:29PM +0000, Roberts, William C wrote:
> Currently the https://github.com/tpm2-software/tpm2-software-container/pulls
> Docker build file has one branch and one Dockerfile. The Dockerhub is configured
> To build the contents of branch master and tag as the latest.
>
> If we want to utilize dockerhub to build multiple images and extend our build coverage,
> This seems limited. Dockerhub has the ability to follow any branch and associate a tag.
> I'm thinking that we create branches for each base image, like:
> - branch: ubuntu-16.04
> - ubuntu-18.04
> - fedora-29
> - fedora-30
> - opensuse-tumbleweed
> - opensuse-leap
> - etc
>
> Those branches can be mapped in the Docker build UI to build a similarly named file.
> The base image that our dockerfile extends is the image in the tag name. Ie branch
> ubuntu-18.04's Dockerfile starts with FROM ubuntu:18.04.
>
> And then in a travis build file, just specify the matrix of images to test against.
>
> Thoughts, ideas objections are welcome. I am **not** a Docker expert.
>
> Thanks,
> Bill
>
Sounds like a great plan to me.
Thanks,
John
next reply other threads:[~2019-08-28 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 21:05 Andersen, John [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-30 17:12 [tpm2] Docker Images Roberts, William C
2019-08-30 17:00 Matthew Dempsky
2019-08-30 15:27 Roberts, William C
2019-08-29 17:39 Matthew Dempsky
2019-08-29 16:40 Roberts, William C
2019-08-28 23:36 Matthew Dempsky
2019-08-28 22:26 Roberts, William C
2019-08-28 20:19 Roberts, William C
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=20190828210511.GF14525@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