automation: drop container name from containerize

This was something that existed for some scripting support for a totally
unrelated project and when I copied this script I failed to remove it so
this removes it. Build containers for Xen are best as ephemeral
environments and should just utilizes Docker's default container naming
behavior.

Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
This commit is contained in:
Doug Goldstein authored and Wei Liu committed 2018-08-03 16:11:22 +01:00
1 parent 7d217430d6
commit f437ac101f
2 files changed
+1 -11

No files matched your search

-5
View File
@@ -53,11 +53,6 @@ understands.
- XEN_CONFIG_EXPERT: If this is defined in your shell it will be
automatically passed through to the container.
- CONTAINER_NAME: By default the container name is set based on the
container itself so that its easy to attach other terminals to your
container. This however prevents you from running multiple containers
of the same version. Override the name value to cause it to name
the container differently on start.
Building a container
--------------------
+1 -6
View File
@@ -65,11 +65,6 @@ if [[ -n ${SSH_AUTH_SOCK} ]]; then
fi
fi
# if we got the CONTAINER_NAME env variable then use that for our name
if [[ -n ${CONTAINER_NAME} ]]; then
name="--name ${CONTAINER_NAME}"
fi
# Figure out the base of what we want as our sources
# by using the top of the git repo
if [[ -z ${CONTAINER_PATH} ]]; then
@@ -85,7 +80,7 @@ exec docker run \
-v "${HOME}/.ssh":/root/.ssh:ro \
${SSH_AUTH_DIR:+-v "${SSH_AUTH_DIR}":/tmp/ssh-agent} \
${XEN_CONFIG_EXPERT:+-e XEN_CONFIG_EXPERT=${XEN_CONFIG_EXPERT}} \
${CONTAINER_ARGS} ${name} \
${CONTAINER_ARGS} \
-${termint}i --rm -- \
${CONTAINER} \
${cmd}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.