Linux Server Bootstrap Script¶
Introduction¶
DevOps work depends on Linux fundamentals: services, logs, networking, permissions, packages, automation, and repeatable deployments. This guide applies those fundamentals to linux server bootstrap script.
Why This Matters for DevOps¶
Automation fails when the host is not predictable. A deployment script, CI runner, container host, or Kubernetes node needs clear packages, permissions, services, logs, and rollback steps.
Core Concepts¶
Key areas for this topic are interface state, subnet mask, default gateway, routes, DNS, and NetworkManager profiles. Keep manual commands and automation aligned so the same result can be recreated on another host.
Practical Examples¶
ip -br addr
ip route show
ping -c 3 192.0.2.1
traceroute 8.8.8.8
Automation Examples¶
#!/usr/bin/env bash
set -euo pipefail
echo "checking host state"
ip -br addr
ip route show
Verification¶
nmcli connection show
Expected evidence:
default via 192.0.2.1 dev eth0 proto static metric 100
eth0 UP 192.0.2.10/24
Common Mistakes¶
- Making several changes at once, which hides the real cause.
- Skipping logs or verification commands after a change.
- Assuming the problem is fixed because one command returned successfully.
Real-World Use Case¶
Use this pattern when preparing servers for CI jobs, application deployment, container runtime setup, log collection, or recovery tasks. The same checks should run before and after the change.
Related Guides¶
- Bash Scripting For DevOps
- Linux Logs For DevOps
- Linux Troubleshooting For DevOps
- Linux DevOps Checklist
Summary¶
DevOps on Linux is reliable when system state is visible and repeatable. Turn proven commands into scripts only after you know how to verify the result.