Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

apiaryio/docker-base-images

Repository files navigation

Build Status

Apiary Docker images

This repository helps keep Apiary environment, services and libraries consistent and in sync.

Each directory has an area of responsibility and the libraries should derive from the respective image.

To keep the image size to its minimum, images are usually derived from minimal Debian image (apiaryio/debian-minimal) or Alpine Linux.

Libraries use the minimal stack available.

Some of the images use tags to differentiate between versions of an underlying library/system, such as apiaryio/coreapp image might be built on different Node.js versions. If this is the case, each tag has a separate Dockerfile in a folder with a tag name:

     ./coreapp
     ./coreapp/0.10/Dockerfile
     ./coreapp/0.12/Dockerfile

Usage and maintenance

  1. Drill into the respective directory

  2. If doing major/arch change, update REFRESHED_AT in the Dockerfile

  3. Build the Docker image with the tag expressed below:

    $ (sudo) docker build -t "apiaryio/$name:$tag" .
  4. Upload it to DockerHub

    $ (sudo) docker push -t "apiaryio/$name:$tag"
  5. When building Apiary app, use the proper FROM: directive inside your Dockerfile

Adding a new image

  1. Create a new repository for apiaryio in DockerHub.
  2. Set Collaborators for that repository to SRE with admin rights.
  3. Add a folder with the image name to this repository structure, e.g. coreapp
  4. If multiple versions are needed, add subfolders with the tag names to the image folder, e.g. 8-chrome-stable.
  5. Build your image locally with $ (sudo) docker build -t "apiaryio/$name:$tag" .to make sure it works. You can skip the $tag and then latest will be used by default.
  6. Log in to Docker Hub using $ docker login from the CLI if you haven't already.
  7. If the image was built correctly, push it to the repository with $ (sudo) docker push -t "apiaryio/$name:$tag"

Images are built automatically on Wercker. Builds on master branch include a deploy step with pushing the built images to DockerHub. If you add a new image as described above, your image will get built and pushed automatically once the changes are merged.

Dredd docker image

Dredd is an HTTP API testing tool. You can find out more about it at its documentation or its code repository. Its Docker image apiaryio/dredd has been moved to a separate repository.

About

Base docker images for Apiary applications

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published