Diff on those two commands :
docker run -d \
–name=node-exporter \
–restart=always \
–net=”host” \
–pid=”host” \
-v “/:/host:ro” \
–log-driver json-file \
–log-opt max-size=10m \
–log-opt max-file=45 \
quay.io/prometheus/node-exporter:latest \
–path.rootfs=/host
docker run -d \
–name=node-exporter \
–restart=always \
–net=”host” \
–pid=”host” \
-v “/:/host:ro” quay.io/prometheus/node-exporter:latest –path.rootfs=/host
Both commands are designed to spin up the Prometheus Node Exporter to monitor your host machine’s physical hardware. While they look nearly identical, the first command is production-ready, while the second command has a hidden trap that can eventually crash your server.
Here is the exact breakdown of the two major differences between them.
Difference 1: Log Rotation (The Crucial Difference)
The primary difference lies in these three lines present only in the first command:
Bash
--log-driver json-file \--log-opt max-size=10m \--log-opt max-file=45 \
The First Command (Safe & Controlled)
This explicitly configures Docker’s logging mechanisms. It tells Docker:
- Treat container logs as standard JSON files.
max-size=10m: Once Node Exporter’s log file reaches 10 Megabytes, roll it over and start a new one.max-file=45: Keep a maximum of 45 old log files.
This sets a strict upper bound on how much space Node Exporter’s logs can take up on your host: $45 \times 10\text{ MB} = 450\text{ MB}$ maximum.
The Second Command (The Hidden Danger)
Because it omits these lines, it uses your system’s default Docker logging behavior. By default, Docker does not limit log file sizes.
If Node Exporter encounters a continuous warning or error (for example, if a specific disk partition becomes unreadable), it will spam logs rapidly. Without a cap, that single log file will grow to 10 GB, 50 GB, or more, until it completely consumes your host’s hard drive and locks up the server.
Difference 2: Readability and Syntax
The second difference comes down to formatting and execution safety.
- First Command: Uses the backslash (
\) at the end of every line. This tells the Linux terminal, “This command isn’t finished yet, continue reading on the next line.” It makes the script highly readable and easy to modify. - Second Command: Missing the backslashes. If you attempt to copy and paste the second block exactly as it is typed into a standard Linux terminal, it will break. The terminal will try to execute
docker run -dby itself on line 1, fail because it has no image name, and then treat the remaining lines as separate, unrecognized commands.
Summary Matrix
| Feature | Command 1 (With Log Options) | Command 2 (Without Log Options) |
| Maximum Disk Used by Logs | Capped at 450 MB | Infinite (Will grow until disk is full) |
| Log Files Auto-Cleaned? | Yes, old logs are purged automatically. | No, requires manual intervention or a global Docker daemon config. |
| Terminal Copy-Paste Ready | Yes (Clean line breaks via \). | No (Will fail unless flattened into a single line). |
Which one should you use?
Always use the first command. When you are managing + 20 different production servers, you cannot afford to have a single chatty container quietly fill up a local hard drive. The first command ensures predictable storage safety.
