<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Non-Root Users on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/non-root-users/</link><description>Recent content in Non-Root Users on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/non-root-users/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing Containers with Non-Root Users and Resource Limits</title><link>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/securing-containers-non-root-users-resource-limits/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/securing-containers-non-root-users-resource-limits/</guid><description>&lt;p&gt;Running applications in production demands not just functionality but also robust security and stable performance. A common oversight in container deployments is operating services with excessive privileges or without proper resource constraints. This can turn a minor vulnerability into a critical system compromise or a simple traffic spike into a cascading outage.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll implement two fundamental production best practices for Docker containers: running services as non-root users and defining explicit CPU and memory limits. These measures significantly reduce your application&amp;rsquo;s attack surface and ensure predictable resource consumption, making your multi-service stack more resilient.&lt;/p&gt;</description></item></channel></rss>