Okay this was a bunch more work than I was expecting, but I finally got it
Things to note:
Some Dockerfiles have new names and live in new locations (either in
faucetsdn/faucet repo or new repos under faucetsdn/*)
Base image for pi images is now multiarch/alpine:armhf-v3.7 (so we can
crossbuild these on x86), I tested on pi2 and pi3 and this seems to work
I renamed a bunch of docker image names on docker hub to be shorter:
- faucet/faucet-base => faucet/base
- faucet/faucet-base-pi => faucet/base-pi
- faucet/faucet-python3 => faucet/python3
- faucet/faucet-python3-pi => faucet/python3-pi
- faucet/faucet-event-adapter-rabbitmq =>
- faucet/faucet-event-adapter-rabbitmq-pi =>
I will keep the old images published under the original names for about a
month on docker hub so that you can have time to update script names etc,
note these dockers will be frozen at their current versions and will not
If you wish to request new docker images in future (for nfv applications
that work with faucet for example), please open an issue on the
faucetsdn/faucet repo and I will action these by creating new git repos.
On Tue, May 1, 2018 at 11:56 AM, defermat <defermat(a)gmail.com> wrote:
Yeah, that sounds like a fine way to do it.
On Mon, Apr 30, 2018 at 4:22 PM Brad Cowie <brad(a)waikato.ac.nz> wrote:
> Good question, I hadn't thought of the docker-compose files.
> I would assume we would keep these in the faucetsdn/faucet repo and we
> can change the build URL to point at the newly formed git repos
> (docker-compose added remote URL support here: https://github.com/docker/
> Does that sound workable?
> On Tue, May 1, 2018 at 10:56 AM, defermat <defermat(a)gmail.com> wrote:
>> Seems reasonable. What would be the proposed path for docker-compose
>> On Mon, Apr 30, 2018 at 3:24 PM, Josh Bailey <joshb(a)google.com> wrote:
>>> That'd be great - the pattern of lots of FAUCET dockers is clearly
>>> established so having a way to manage them/with minimal dependencies would
>>> be great.
>>> On Tue, May 1, 2018 at 10:16 AM Brad Cowie <brad(a)waikato.ac.nz> wrote:
>>>> Hi team,
>>>> I think at this point we've pretty much hit peak Dockerfile in the
>>>> faucetsdn/faucet repo (I count 19 in there currently). As it is I get
>>>> forgetful of what each one does and how to build them and I fear this
>>>> situation will only get worse as time goes on and we increase the number
>>>> NFV Dockers we supply.
>>>> What I am proposing we remove any Dockerfiles that don't directly
>>>> depend on our faucet code base (think the base images and hostapd etc)
>>>> moving these into their own repos.
>>>> The benefits are that these Dockers will become decoupled from the
>>>> regular faucet release cycle (this will help us out in the situation one
>>>> these Dockers break and we will be able to fix it without burning a
>>>> version number, also will help with out of band security patches to
>>>> images). We will also be able to more effectively trigger builds when
>>>> Dockers change rather than the current strategy of building them
>>>> we bump the faucet version.
>>>> The downside is that there may be some slight code duplication between
>>>> the new Dockerfile repos where we need to ship setupproxy.sh etc, but I
>>>> think the benefits here out way the negatives.
>>>> I am of course offering to do all the work, just wondering if anyone
>>>> objects or has any brighter ideas?
>>>> Faucet-dev mailing list
>>> Faucet-dev mailing list
Department of Computer Science
The University of Waikato
Phone: +64 7 858 5267
Mobile: +64 27 5888 103