This repository is deprecated, see instead.
56.2 MB
All Layers
Find file
Last update
over 3 years ago
over 3 years ago
over 1 year ago
over 3 years ago
over 3 years ago
over 3 years ago
over 3 years ago
over 3 years ago
over 1 year ago
over 3 years ago
over 3 years ago
over 3 years ago
over 3 years ago
almost 3 years ago
over 3 years ago
over 3 years ago

newman-docker logo


This repository contains docker images for Newman.

Newman is a command-line collection runner for Postman. It allows you to effortlessly run and test a Postman Collections directly from the command-line. It is built with extensibility in mind so that you can easily integrate it with your continuous integration servers and build systems.

New to Docker? Docker allows you to package an application with all of its dependencies into a standardised unit for software development. Visit to read more about how docker can drastically simplify development and deployment.

Using the docker image

The docker image for Newman is available for download from our docker hub. You must have Docker installed in your system. Docker has extensive installation guideline for popular operating systems. Choose your operating system and follow the instructions.

Ensure you that you have docker installed and running in your system before proceeding with next steps. A quick test to see if docker is installed correctly is to execute the command docker run hello-world and it should run without errors.

Step 1:

Pull the newman docker image from docker hub:

docker pull postman/newman_alpine33;

Step 2:

Run newman commands on the image:

docker run -t postman/newman_alpine33 --url=""

Build the docker image from this repository

Step 1:

Clone this repository:

git clone

Step 2:

Build the image:

docker build -t postman/newman_alpine33 images/alpine33

Step 3:

Run a collection using the newman image:

docker run -t postman/newman_alpine33 --url=""

Running local collection files

This docker image is designed to pick files from the /etc/newman directory within the image. You may mount the directory of your collection files into that location and provide the file references in standard newman parameters.

# Mount host collections folder ~/collections, onto /etc/newman on the docker image, so that newman
# has access to collections
docker run -v ~/collections:/etc/newman -t postman/alpine33 --collection="HTTPBinNewmanTest.json.postman_collection"

You are not required to mount a volume if you do not need to save newman report to the host, and your collection is available online, unless your collection requires an environment (as environments cannot be passed as URLs).

To know more about mounting volumes, visit docker documentation on shared data volumes.


Run a local collection, pass an environment to it, and save the HTML report on the host.

docker run -v ~/collections:/etc/postman -t postman/newman_alpine33 \
    --collection="HTTPBinNewmanTest.json.postman_collection" \
    --environment="HTTPBinNewmanTest.json.postman_environment" \

Run a remote collection, pass it a local environment, and save JUnit XML test report on the host

docker run -v ~/collections:/etc/postman -t postman/newman_alpine33 \
    --url="" \
    --environment="HTTPBinNewmanTest.json.postman_environment" \

Import a Postman backup file, and save collections, environments, and globals

docker run -v ~/collections:/etc/postman -t postman/alpine33 --import="Backup.postman_dump" --pretty

Use a script to run a collection and do something, for example deploy the build, if all the tests pass


# Stop on first error
set -e;

function onExit {
    if [ "$?" != "0" ]; then
        echo "Tests failed";
        # build failed, don't deploy
        exit 1;
        echo "Tests passed";
        # deploy build

trap onExit EXIT;

docker run -t postman/newman_alpine33 --url="" --exitCode;