Fixes:
Fixes:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env bash | |
usage() | |
{ | |
cat <<EOF | |
Armory Docker Build Script " | |
This build script helps to build the docker images necessary for armory exectuion | |
The primary purpose of this script is to build the images from scratch and to be | |
used by the armory CI toolchain. |
In order to get this to run, I needed to backtrack through the scenario as stored in GARD evaluations. My "travelogue" follows the "How To" in case I need to recapitulate this again for another job.
First make things look like a "standard" armory installation:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Network services, Internet style | |
# | |
# Note that it is presently the policy of IANA to assign a single well-known | |
# port number for both TCP and UDP; hence, officially ports have two entries | |
# even if the protocol doesn't support UDP operations. | |
# | |
# Updated from http://www.iana.org/assignments/port-numbers and other | |
# sources like http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/services . | |
# New ports will be added on request if they have been officially assigned | |
# by IANA and used in the real-world or are needed by a debian package. |