How to use nix-shell -p for quick temporary packages
| OS / Distro | NixOS |
|---|---|
| Category | Operating Systems |
| Guide type | Procedure |
| Skill level | Intermediate to advanced |
| Time | 15 - 60 minutes including verification |
When How to use nix-shell -p for quick temporary packages bites you on NixOS, the first instinct is to open a support ticket. Most of the time you do not have to. The steps below are the ones a senior Linux engineer would walk you through on a war-room call.
What how to use nix-shell -p for quick temporary packages actually involves on NixOS
This task on NixOS is one of the more searched operational topics across distro forums and Unix StackExchange in the last 12 months. The procedure below is the path that works on a current NixOS install with default config.
The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing in production.
Diagnose first, fix second
Diff against last known good. The last config change you made is the cause about three quarters of the time, even when the change should not have mattered. Use etckeeper log, snapper diff, ZFS snapshot diff, or your Git history on /etc to see the actual delta between the state when it worked and when it broke. The change you remember is rarely the only change that happened.
Reproduce the failure with the relevant CLI in verbose or debug mode. apt -o Debug::pkgProblemResolver=true, dnf -v, zypper --verbose, pacman -dvv, systemctl status --no-pager -l, and strace -f -e trace=openat,read,write all expose what the high-level error message hides. Save the debug output to a file so you can grep it later instead of scrolling.
Start by capturing the exact error string verbatim. Many UIs and installers truncate messages in popups, but the system log keeps the full record. Use journalctl -xe on systemd distros, logread on OpenWrt, dmesg for kernel messages, /var/log/messages on RHEL family, /var/log/syslog on Debian family. For ESXi use vmkernel.log in the DCUI. For Solaris use fmadm faulty. For AIX use errpt -a. The exact error code (for example NO_PUBKEY, 0x803fb112, NodeCreationFailure, NW-2-5) is the thing you grep for in forums and Stack Exchange, not the human-readable sentence next to it.
Solution-focused remediation path
Most NixOS failures fall into one of three buckets: configuration drift (a setting changed and nobody documented it), dependency gap (a package, kernel module, or library is missing or wrong version), or resource exhaustion (disk, memory, file handles, or inodes). Triage in that order. It covers around 80 percent of real-world cases. If the failure does not fit any of the three, it is likely an upstream regression worth tracking against the distro bug tracker.
If the issue points at packages, do not start by force-removing them. Run apt --fix-broken install on Debian family, dnf check + dnf distro-sync on RHEL family, zypper verify + zypper dup on openSUSE, pacman -Syu on Arch. Force-removing a held-back package is the fastest way to break apt or dnf so badly the next boot lands in single-user mode.
If you cannot reproduce the failure consistently, the cause is probably a race condition, a session-cache issue, or environment drift between two hosts that should be identical. Run the failing operation under strace -f -e trace=openat,connect,read,write -o /tmp/trace in one terminal and a second known-good instance in another. Diff the trace files. The first divergence is almost always the bug.
Automate this fix so you do not do it twice
Codify the fix as a systemd timer or cron job for unattended remediation
For workflows that need to run unattended (clear a stuck cache, rotate logs, fail over a service, rebuild an index) a systemd timer or a cron job is the right place. Timers can fire on boot, on schedule, or after a dependency unit reaches an active state. systemctl list-timers shows the next-fire time for every active timer. For interactive helper workflows, a wrapper shell script in /usr/local/bin/ documented in MOTD or the team wiki keeps the institutional knowledge accessible.
Add a manual-approval gate with sudo and auditd for risky fixes
For multi-step fixes that include a destructive action (drop a database, delete a snapshot, fail over a cluster, wipe a partition) gate the script behind sudo with an auditd rule that logs every invocation. The audit trail lives in /var/log/audit/audit.log with the invoking UID and GID and the exact command. For change management requiring a second-person sign-off, wrap the destructive step in a configuration-management approval gate such as Ansible Tower or AWX, Puppet Enterprise, or Salt Master ACL.
Add a Prometheus alert or Zabbix trigger so you catch the next occurrence
The cheapest way to never see the same incident twice is a monitoring rule that watches for the symptom (a specific log line, a metric threshold, a service state) and fires into Slack, PagerDuty, or a webhook when it trips. For NixOS the relevant signals come from journalctl filters fed to a log shipper, Prometheus exporters such as node_exporter or blackbox_exporter or a service-specific exporter, and structured log forwarders such as Fluent Bit, Vector, or syslog-ng. Set thresholds against observed normal range, not round numbers.
Common pitfalls and what to watch for
The most common pitfall when fixing this on NixOS is treating it as a one-off rather than as a recurring class of incident. The same misconfiguration tends to happen again after a kernel upgrade, a major distro version bump, or a fleet rollout unless the fix is codified. Add an Ansible role, a Puppet manifest, a SaltStack state, or a Cloud-init drop-in that prevents the same misconfig from being reintroduced. Documentation alone does not survive team turnover.
Another common trap: confirming the fix on a single host and assuming the fleet is healthy. Loop your check across every node, container, and VM that could exhibit the same symptom. If you cannot enumerate the affected scope without a script, you do not yet understand the scope.
Verify the fix worked
- Reproduce the original symptom path. If it still surfaces on any host, container, or VM in the fleet, you have not fixed it.
- Watch for 24 to 48 hours.
journalctl --since '24 hours ago' -u <service> -p errand Prometheus query history can mask issues with cached health for 6 to 12 hours, especially for slow-burn memory leaks and disk-fill regressions. - Run a smoke test under realistic load. Happy-path tests miss race conditions, file-descriptor leaks, and cgroup limits.
- Capture the new state in a runbook so the next person on call does not have to rediscover this. Push it to Confluence or your team wiki, not into Slack.
- If the fix involved a permission or security change, run a CIS Benchmark or DISA STIG audit one more time to confirm you did not open a separate hole while closing this one.
Safety, rollback, blast radius
- Test in a non-production VM, container, or namespace if your environment supports it. The cost of one disposable VM is cheaper than one rollback meeting.
- Export the existing config before changing it. Most NixOS services support
--print-defaults,systemctl show, or a documented config-dump command. Capture that to source control before you start. - Know your rollback path. Some NixOS operations are one-way (irreversible filesystem upgrade like ext3 to ext4 inline, kernel ABI change, removal of an LVM physical volume). Confirm reversibility on the official OS documentation before you commit.
- Be aware of cross-service impact. A change to PAM ripples to every service using it. A change to /etc/resolv.conf affects every name lookup. A change to systemd default.target affects every reboot.
- Maintenance window discipline: if the change touches DNS, certificate rotation, kernel upgrade, or anything that emits TLS handshakes, line up a window with stakeholder notification, not a heroic mid-day swap.
FAQ
etckeeper commit, cp file file.bak.$(date +%F), or a Btrfs/ZFS snapshot), then commit it before you change anything. A few operations are one-way (in-place filesystem conversion, partition table rewrite, kernel ABI bump). Check the distro release notes for the specific operation before you commit.systemctl list-dependencies and lsof to enumerate consumers before changing a shared service or configuration file.man <command> on the host, or the upstream project documentation - those almost always still work.sosreport (RHEL family) or supportconfig (SUSE), and your reproduction steps. The distro forum is the no-cost public alternative - search there first; 80 percent of common NixOS issues already have a working answer marked as solved.References
- Official documentation for NixOS
- Distro forums and community Q&A (Ubuntu Discourse, Fedora Discussion, Arch BBS, openSUSE Forum, Reddit r/linux + distro subreddits, ServerFault, Unix StackExchange)
- Vendor status pages and release-notes feeds
- CIS Benchmarks and DISA STIG hardening guides for NixOS
Related fixes
Related guides worth a look while you sort this one out: