aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTin Lam <tinlam@gmail.com>2016-11-25 00:14:20 -0600
committerTin Lam <tinlam@gmail.com>2016-11-25 16:13:42 -0600
commit661f2a45c26de322000ac6739bb1cea9c4b761d6 (patch)
tree827e8ee00e4d6074e74a650185ebc253d1c0eb63 /doc
parenta8a1c4cc3d0f42e96e0436d9125614cd2c3679fd (diff)
downloadkolla-661f2a45c26de322000ac6739bb1cea9c4b761d6.tar.gz
kolla-661f2a45c26de322000ac6739bb1cea9c4b761d6.zip
Remove --include-header and --include-footer parameter
In Newton, kolla moved to Dockerfile customization, and the parameters --included-header and --include-footer were marked deprecated. This patch set removes them in the Ocata release. Change-Id: I3263c305bf619ab47a31cf4eafe5d4fcfa4aec17 Closes-Bug: #1643967
Diffstat (limited to 'doc')
-rw-r--r--doc/image-building.rst31
1 files changed, 7 insertions, 24 deletions
diff --git a/doc/image-building.rst b/doc/image-building.rst
index a4ce5bb2d..96a14e07a 100644
--- a/doc/image-building.rst
+++ b/doc/image-building.rst
@@ -145,21 +145,14 @@ the best use of the docker cache.
type = local
location = /tmp/ironic.tar.gz
-To build RHEL containers, it is necessary to use the ``-i`` (include header)
-feature to include registration with RHN of the container runtime operating
-system. To obtain a RHN username/password/pool id, contact Red Hat.
-
-First create a file called ``rhel-include``:
-
-::
+To build RHEL containers, it is necessary to include registration with RHN
+of the container runtime operating system. To obtain a RHN
+username/password/pool id, contact Red Hat. Use a template's header block
+overrides file, add the following::
RUN subscription-manager register --user=<user-name> --password=<password> \
&& subscription-manager attach --pool <pool-id>
-Then build RHEL containers::
-
- kolla-build -b rhel -i ./rhel-include
-
Dockerfile Customisation
========================
@@ -371,32 +364,22 @@ insecure registry. See
Building behind a proxy
-----------------------
-The build script supports augmenting the Dockerfiles under build via so called
-`header` and `footer` files. Statements in the `header` file are included at
-the top of the `base` image, while those in `footer` are included at the bottom
-of every Dockerfile in the build.
-
-A common use case for this is to insert http_proxy settings into the images to
+We can insert http_proxy settings into the images to
fetch packages during build, and then unset them at the end to avoid having
them carry through to the environment of the final images. Note however, it's
not possible to drop the info completely using this method; it will still be
visible in the layers of the image.
-To use this feature, create a file called ``.header``, with the following
-content for example::
+To set the proxy settings, we can add this to the template's header block::
ENV http_proxy=https://evil.corp.proxy:80
ENV https_proxy=https://evil.corp.proxy:80
-Then create another file called ``.footer``, with the following content::
+To unset the proxy settings, we can add this to the template's footer block::
ENV http_proxy=""
ENV https_proxy=""
-Finally, pass them to the build script using the ``-i`` and ``-I`` flags::
-
- kolla-build -i .header -I .footer
-
Besides this configuration options, the script will automatically read these
environment variables. If the host system proxy parameters match the ones
going to be used, no other input parameters will be needed. These are the