From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sun, 7 Apr 2024 13:41:34 -0500
Subject: new repository

---
 devdocs/vagrant/docker%2Fconfiguration.html | 33 +++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 devdocs/vagrant/docker%2Fconfiguration.html

(limited to 'devdocs/vagrant/docker%2Fconfiguration.html')

diff --git a/devdocs/vagrant/docker%2Fconfiguration.html b/devdocs/vagrant/docker%2Fconfiguration.html
new file mode 100644
index 00000000..87e132f9
--- /dev/null
+++ b/devdocs/vagrant/docker%2Fconfiguration.html
@@ -0,0 +1,33 @@
+<h1 id="docker-configuration">  Docker Configuration </h1> <p>The Docker provider has some provider-specific configuration options you may set. A complete reference is shown below.</p> <h3 id="required">  Required </h3> <p>One of the following settings is required when using the Docker provider:</p> <ul> <li>
+<p><a href="#build_dir"><code>build_dir</code></a> (string) - The path to a directory containing a Dockerfile.</p> </li> <li>
+<p><a href="#image"><code>image</code></a> (string) - The image to launch, specified by the image ID or a name such as <code>ubuntu:12.04</code>.</p> </li> <li>
+<p><a href="#git_repo"><code>git_repo</code></a> (string) - The URL of a git repository to build the image from. Supports pulling specific tags, branches and revision, consult the <a href="https://docs.docker.com/engine/reference/commandline/build/#/git-repositories">docker documenation</a> for more information.</p> </li> </ul> <h3 id="optional">  Optional </h3> <p>General settings:</p> <ul> <li>
+<p><a href="#build_args"><code>build_args</code></a> (array of strings) - Extra arguments to pass to <code>docker build</code> when <code>build_dir</code> is in use.</p> </li> <li>
+<p><a href="#cmd"><code>cmd</code></a> (array of strings) - Custom command to run on the container. Example: <code>["ls", "/app"]</code>.</p> </li> <li>
+<p><a href="#compose"><code>compose</code></a> (boolean) - If true, Vagrant will use <code>docker-compose</code> to manage the lifecycle and configuration of containers. This defaults to false.</p> </li> <li>
+<p><a href="#compose_configuration"><code>compose_configuration</code></a> (Hash) - Configuration values used for populating the <code>docker-compose.yml</code> file. The value of this Hash is directly merged and written to the <code>docker-compose.yml</code> file allowing customization of non-services items like networks and volumes.</p> </li> <li>
+<p><a href="#create_args"><code>create_args</code></a> (array of strings) - Additional arguments to pass to <code>docker run</code> when the container is started. This can be used to set parameters that are not exposed via the Vagrantfile.</p> </li> <li>
+<p><a href="#dockerfile"><code>dockerfile</code></a> (string) - Name of the Dockerfile in the build directory. This defaults to "Dockerfile"</p> </li> <li>
+<p><a href="#env"><code>env</code></a> (hash) - Environmental variables to expose into the container.</p> </li> <li>
+<p><a href="#expose"><code>expose</code></a> (array of integers) - Ports to expose from the container but not to the host machine. Useful for links.</p> </li> <li>
+<p><a href="#link"><code>link</code></a> (method, string argument) - Link this container to another by name. The argument should be in the format of <code>(name:alias)</code>. Example: <code>docker.link("db:db")</code>. Note, if you are linking to another container in the same Vagrantfile, make sure you call <code>vagrant up</code> with the <code>--no-parallel</code> flag.</p> </li> <li>
+<p><a href="#force_host_vm"><code>force_host_vm</code></a> (boolean) - If true, then a host VM will be spun up even if the computer running Vagrant supports Linux containers. This is useful to enforce a consistent environment to run Docker. This value defaults to "false" on Linux, Mac, and Windows hosts and defaults to "true" on other hosts. Users on other hosts who choose to use a different Docker provider or opt-in to the native Docker builds can explicitly set this value to false to disable the behavior.</p> </li> <li>
+<p><a href="#has_ssh"><code>has_ssh</code></a> (boolean) - If true, then Vagrant will support SSH with the container. This allows <code>vagrant ssh</code> to work, provisioners, etc. This defaults to false.</p> </li> <li>
+<p><a href="#host_vm_build_dir_options"><code>host_vm_build_dir_options</code></a> (hash) - Synced folder options for the <code>build_dir</code>, since the build directory is synced using a synced folder if a host VM is in use.</p> </li> <li>
+<p><a href="#name"><code>name</code></a> (string) - Name of the container. Note that this has to be unique across all containers on the host VM. By default Vagrant will generate some random name.</p> </li> <li>
+<p><a href="#pull"><code>pull</code></a> (bool) - If true, the image will be pulled on every <code>up</code> and <code>reload</code>. Defaults to false.</p> </li> <li>
+<p><a href="#ports"><code>ports</code></a> (array of strings) - Ports to expose from the container to the host. These should be in the format of <code>host:container</code>.</p> </li> <li>
+<p><a href="#remains_running"><code>remains_running</code></a> (boolean) - If true, Vagrant expects this container to remain running and will make sure that it does for a certain amount of time. If false, then Vagrant expects that this container will automatically stop at some point, and will not error if it sees it do that.</p> </li> <li>
+<p><a href="#stop_timeout"><code>stop_timeout</code></a> (integer) - The amount of time to wait when stopping a container before sending a SIGTERM to the process.</p> </li> <li>
+<p><a href="#vagrant_machine"><code>vagrant_machine</code></a> (string) - The name of the Vagrant machine in the <code>vagrant_vagrantfile</code> to use as the host machine. This defaults to "default".</p> </li> <li>
+<p><a href="#vagrant_vagrantfile"><code>vagrant_vagrantfile</code></a> (string) - Path to a Vagrantfile that contains the <code>vagrant_machine</code> to use as the host VM if needed.</p> </li> <li>
+<p><a href="#volumes"><code>volumes</code></a> (array of strings) - List of directories to mount as volumes into the container. These directories must exist in the host where Docker is running. If you want to sync folders from the host Vagrant is running, just use synced folders.</p> </li> </ul> <p>Below, we have settings related to auth. If these are set, then Vagrant will <code>docker login</code> prior to starting containers, allowing you to pull images from private repositories.</p> <ul> <li>
+<p><a href="#email"><code>email</code></a> (string) - Email address for logging in.</p> </li> <li>
+<p><a href="#username"><code>username</code></a> (string) - Username for logging in.</p> </li> <li>
+<p><a href="#password"><code>password</code></a> (string) - Password for logging in.</p> </li> <li>
+<p><a href="#auth_server"><code>auth_server</code></a> (string) - The server to use for authentication. If not set, the Docker Hub will be used.</p> </li> </ul><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
+    <a href="https://www.vagrantup.com/docs/docker/configuration.html" class="_attribution-link">https://www.vagrantup.com/docs/docker/configuration.html</a>
+  </p>
+</div>
-- 
cgit v1.2.3