mirror of
https://github.com/docker/docs.git
synced 2026-04-12 06:19:22 +07:00
config: use "console" for shell examples
This allows for easier copying of the commands, without selecting the prompt. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
@@ -48,7 +48,7 @@ configuration.
|
||||
When you start Docker this way, it runs in the foreground and sends its logs
|
||||
directly to your terminal.
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ dockerd
|
||||
|
||||
INFO[0000] +job init_networkdriver()
|
||||
@@ -98,8 +98,8 @@ This can be useful for troubleshooting problems.
|
||||
Here's an example of how to manually start the Docker daemon, using the same
|
||||
configurations as above:
|
||||
|
||||
```bash
|
||||
dockerd --debug \
|
||||
```console
|
||||
$ dockerd --debug \
|
||||
--tls=true \
|
||||
--tlscert=/var/docker/server.pem \
|
||||
--tlskey=/var/docker/serverkey.pem \
|
||||
@@ -274,7 +274,7 @@ Docker platform.
|
||||
3. Send a `HUP` signal to the daemon to cause it to reload its configuration.
|
||||
On Linux hosts, use the following command.
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ sudo kill -SIGHUP $(pidof dockerd)
|
||||
```
|
||||
|
||||
@@ -292,7 +292,7 @@ by sending a `SIGUSR1` signal to the daemon.
|
||||
|
||||
- **Linux**:
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ sudo kill -SIGUSR1 $(pidof dockerd)
|
||||
```
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ either IPv4 or IPv6 (or both) with any container, service, or network.
|
||||
|
||||
2. Reload the Docker configuration file.
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ systemctl reload docker
|
||||
```
|
||||
|
||||
|
||||
@@ -210,7 +210,7 @@ Next, start a single-replica Prometheus service using this configuration.
|
||||
|
||||
<div id="linux-run" class="tab-pane fade in active" markdown="1">
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ docker service create --replicas 1 --name my-prometheus \
|
||||
--mount type=bind,source=/tmp/prometheus.yml,destination=/etc/prometheus/prometheus.yml \
|
||||
--publish published=9090,target=9090,protocol=tcp \
|
||||
@@ -220,7 +220,7 @@ $ docker service create --replicas 1 --name my-prometheus \
|
||||
</div><!-- linux -->
|
||||
<div id="mac-run" class="tab-pane fade" markdown="1">
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ docker service create --replicas 1 --name my-prometheus \
|
||||
--mount type=bind,source=/tmp/prometheus.yml,destination=/etc/prometheus/prometheus.yml \
|
||||
--publish published=9090,target=9090,protocol=tcp \
|
||||
@@ -263,7 +263,7 @@ To make the graph more interesting, create some network actions by starting
|
||||
a service with 10 tasks that just ping Docker non-stop (you can change the
|
||||
ping target to anything you like):
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ docker service create \
|
||||
--replicas 10 \
|
||||
--name ping_service \
|
||||
@@ -278,7 +278,7 @@ your graph.
|
||||
When you are ready, stop and remove the `ping_service` service, so that you
|
||||
are not flooding a host with pings for no reason.
|
||||
|
||||
```bash
|
||||
```console
|
||||
$ docker service remove ping_service
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user