* Second open(2) causes copy-up operation
The documentation incorrectly credits the first, read-only call to open as the trigger of the copy-up operation. It's the subsequent read-write call that actually triggers the copy-up operation.
The file that was downloaded was actually the autocompletion for `docker` and not `docker-machine`
I tested the "fix" on my local installation: It's working ;)
If the first grep is already quiet, the second one will not find anything and exit with error code 1. So the quiet flag has to be on the second grep command to get the script working.
* Update install to ensure extras repo is enabled
The `extras` repos are required for 17.06 which depends on the
`container-selinux` package.
CentOS typically has the repo enabled by default, but in some cases may
be disabled, and RHEL never has it enabled by default.
This is provided by the main Fedora repos and does not require any extra
setting.
Signed-off-by: Brian Goff <cpuguy83@gmail.com>
* Jekyll is picky about indentation.
* Jekyll is picky about indentation.
* Specify Compose version for Compose file formats (#3297)
* Specify Compose version for Compose file formats
Explicitly specifying Compose versions file formats 2.1 and 2.2.
* corrected typo 2.1 --> 2.2
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Document new Compose 1.14.0 features (#3695)
Signed-off-by: Joffrey F <joffrey@docker.com>
* Current compose is 1.14.0 (#3690)
Signed-off-by: Guillaume Rose <guillaume.rose@docker.com>
* Fix typo
* Correct command to copy binary
Correct path to copy binary-daemon.
Remove command to copy binary-client (it's not available).
* Use the make install target
Signed-off-by: Misty Stanley-Jones <misty@docker.com>
* add d4mac client side FAQ
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added link to FAQs from Getting Started
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added FAQs re: installing client certificates
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added more detail on client and server side certs
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed Mac and Windows specific topics
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed formatting so that content renders properly
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* incorporated review comments
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* updated Windows FAQ to clarify directories copy, remove refs to db
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* change ref from Mac to Windows on Win side
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added certificate topic to Win getting started
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* review comments, remove 'entities' clarify meaning
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Previous version could not work as grep -q does not print anything to stdout, only exits with a status code depending on a match was found or not. Hence the variables were always empty and could not be compared with 0
* Remove extraneous **warning**
The .warning class already prepends "Warning"
* changed Warning tag to vanilla
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Add notes
After Docker Cloud Agent installed successfully, and run the `docker swarm init` and `docker swarm join` commands will got the errors, and can not register swarm with Docker Cloud.
```
*******************************************************************************
Docker Cloud Agent installed successfully
*******************************************************************************
You can now deploy containers to this node using Docker Cloud
ubuntu@test:~$ docker swarm init
docker: 'swarm' is not a docker command.
See 'docker --help'.
ubuntu@test:~$ sudo docker run -ti --rm -v /var/run/docker.sock:/var/run/docker.sock dockercloud/registration
Unable to find image 'dockercloud/registration:latest' locally
latest: Pulling from dockercloud/registration
79650cf9cc01: Pull complete
e720390eb80b: Pull complete
7b619be6318c: Pull complete
Digest: sha256:b0c89c6a446700394c7b85d93b9b1117e517504c64577586f535ceec353628e7
Status: Downloaded newer image for dockercloud/registration:latest
Error response from daemon: 404 page not found
```
So, `Use the Docker Cloud Agent to Bring your Own Host` does not support swarm mode.
* formatted note, clarified Cloud standard and swarm modes
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits, rewrites
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Without the host and credentials, the `myapp_test` database is not
created, and instead, the user receives a PG error and a long backtrace.
This commit moves the credentials to a default anchor to share across
development and test environments.
The "Docker for AWS / Deploy your app" page has a broken link to
distributed application bundles. There now is a dedicated page within
the documentation repo ("Docker Compose / Docker stacks and distributed
application bundles") that we can reference.
Tracking: #3660https://github.com/docker/docker.github.io/issues/3660
Signed-off-by: John Paul Herold <johnpaul7@gmail.com>
