lifen-postman/node_modules/newman/docker/images/alpine33

newman_alpine33 (deprecated)

Use postman/newman:alpine instead. See https://hub.docker.com/r/postman/newman/ for more available tags

This image runs newman on node v8 on Alpine 3.3

Build the image:

docker build -t postman/newman_alpine33 --build-arg NEWMAN_VERSION="full semver version" .

Or get it from Docker Hub:

docker pull postman/newman_alpine33

Then run it:

docker --volume="/home/postman/collections:/etc/newman" -t postman/newman_alpine33 run JSONBlobCoreAPI.json.postman_collection -r json --reporter-json-export newman-report.json

For newman-docker to be able to use collections and environment files saved on the host machine, and to save reports generated by newman, a directory containing the collection and environment needs to be mounted on to the docker instance on run time, preferably at /etc/newman, which is the default working directory. If you mount to a different location, then:

• You can pass the full path to your collection and environment files to newman. For instance, if you mount to /etc/newman,

docker --volume="/home/postman/collection:/etc/newman" -t postman/newman_alpine33 run JSONBlobCoreAPI.json.postman_collection" -r json --reporter-json-export newman-report.json

• You can change the working directory while running the image to the location you mounted to, using the -w or --workdir flag.

docker run --volume="/home/postman/collections:/etc/newman" -t postman/newman_alpine33 run JSONBlobCoreAPI.json.postman_collection -r json --reporter-json-export newman-report.json

In case you don't need to save newman's report to the host, and your collection is available online and does not require any environment, then you can forgo mounting your collections directory and directly pass the collection URL to newman:

docker run -t postman/newman_alpine33 run https://www.getpostman.com/collections/8a0c9bc08f062d12dcda