Servers and infrastructure
Container registries, SSH transports, and version control on machines you do not fully administer - including the errors that are permission problems and the ones that only look like them.
- Two Azure CLI traps: -o tsv smuggles a carriage return, and az monitor metrics list returns Bad Request
A value captured with -o tsv looks right, echoes right and still breaks the URL you paste it into, and az monitor metrics list rejects valid metrics with a detail-free Bad Request. How to see both and how to get around them.
- Azure will not back up your NFS file share, and will not make it immutable either
Designing a recovery story for an Azure Files NFS share and hitting four separate capability limits — no Azure Backup, no share soft delete under the new provider, no blob WORM, no versioning. The design that survives them.
- Synology NAS: scp fails with "subsystem request failed on channel 0"
DSM ships an SSH server without the sftp subsystem, so scp and sftp both fail even though ssh logs in fine. Transfer files with cat over ssh instead — and do not expect the bundled ffmpeg to encode anything.
- A server-side hook rejects every commit until the message carries the right project token
A Subversion commit to a shared release tree is refused by a pre-commit hook and rolled back, no matter how the message is reworded. Why the rule is path-scoped, how to read it out of history, and how to commit without a checkout.
- docker manifest inspect fails with "permission denied" on /etc/docker/certs.d
A deploy script that pre-checks whether an image tag exists breaks for non-root users on nodes with a private registry CA. The registry API answers anyway — use a plain HTTP HEAD as the fallback.
- Editing a Subversion repository without a working copy: svnmucc
Checking out a release repository just to change one deploy script is slow and error-prone. svnmucc performs put, rm and mv straight against the URL as one atomic commit — including the commit-message prefix a pre-commit hook may demand.