Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/6si/shipwright

Shipwright | The right way to build, tag and ship Docker containers.
https://github.com/6si/shipwright

Last synced: about 1 month ago
JSON representation

Shipwright | The right way to build, tag and ship Docker containers.

Awesome Lists containing this project

README 

        
Shipwright builds shared Docker images within a git repository in **the

right order** and publishes them tagged with git's revision/branch

information so you'll never lose track of an image's origin.



It's the perfect tool for building and publishing your images to places

like Docker Hub or your own private registry. Have a look at `our

motivation `__ to see why we built it and the pain

points it solves for you.



Alternatives

============



See also https://github.com/moby/buildkit



Installation

============



Shipwright is a simple python script you can install with pip



::



    $ pip install shipwright



Quickstart

==========



Once installed, simply change to a project of yours that contains

multiple Dockerfiles and is in git.



Add a json formatted file named ``.shipwright.json`` to the root

directory of your project. At minimum it should contain the version

number of your Shipwright config and a ``namespace`` which is either

your docker hub user name or the URL to your private repository.



1.0 is the current version for the config.



.. code:: json



    {

      "version": 1.0,

      "namespace": "[your docker hub name or private repository]"

    }



Additionally your config file can map directory names to alternative

docker repositories. For example here is a ``.shipwright.json`` for the

docker hub user ``shipwright`` that also maps the root of the git

repository to the docker image ``shipwright/shared`` and the ``/foo``

directory to ``shipwright/awesome_sauce``.



.. code:: json



    {

      "version": 1.0,



      "namespace": "shipwright",

      "names": {

        "/": "shipwright/shared",

        "/foo": "shipwright/awesome_sauce"

    }



Now you can build all the docker images in the git repo by simply

changing to any directory under your git repo and running:



::



    $ shipwright



This will recurse through all the directories, looking for ones that

contain a Dockerfile. Shipwright will build these Dockerfiles in order

and by default tag them with ``/:``

along with ``/:`` and

``/:latest``



Working example

---------------



We have `a sample shipwright

project `__ you can use if you

want to try this out right away.



.. code:: bash



    $ git clone https://github.com/6si/shipwright-sample.git

    $ cd shipwright-sample

    $ shipwright 



**NOTE: you can use any username you'd like while building locally. In

the above example we use ``shipwright``. Nothing is published unless you

use the ``push`` command. For your own projects, substitute

``shipwright`` in the above example with your (or your organizations)

official docker hub username or private repository.**



Notice that if you run the ``shipwright`` a second time it will return

immediately without doing anything. Shipwright is smart enough to know

nothing has changed.



Shipwright really shines when you switch git branches.



.. code:: bash



    $ git checkout new_feature

    $ shipwright



Notice that shipwright only rebuilt the shared library and service1,

ignoring the other projects because they have a common git ancestry.

Running ``docker images`` however shows that all the images in the git

repository have been tagged with the latest git revision, branch and

``latest``.



In fact, as Shipwright builds images it rewrites the Dockerfiles so

that they require the base images with tags from the current git

revision. This ensures that the entire build is deterministic and

reproducible.



Building

========



By default, if you run shipwright with no arguments, it will build all

Dockerfiles in your git repo. You can specify one or more ``specifiers``

to select fewer images to build. For example you can build a single

images and its dependencies by simply specifying its name on the command

line.



::



    $ shipwright /some_image



Run \`shipwright --help' for more examples of specifiers and their uses.



Publishing

==========



With one command Shipwright can build your images and push them to a

remote repository.



::



    $ shipwright push



If you like you can just push your latest images without building.



::



    $ shipwright push --no-build 



The same specifiers for building also work with ``push``. You might use

this to build an entire tree in one step then push a specific image like

so.



::



    $ shipwright build

    $ shipwright push -e /public_image