# Docker image now defaults to non-root user

**URL:** <https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784>\
**Category:** Ignition Early Access\
**Tags:** docker\
**Created:** [February 13, 2023, 6:04pm UTC](https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784 "2023-02-13T18:04:59Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [February 13, 2023, 7:50pm UTC](https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784/5 "2023-02-13T19:50:50Z")

</div>

I should clarify that the Docker image launches that gateway directly, no systemd involved (as is typical in most container images). The capabilities that a container gets when launched is controlled by the container runtime--see some info [here](https://docs.docker.com/engine/security/#linux-kernel-capabilities). There isn't a way to "request" default capabilities within the OCI image definition that I'm aware of.

---

_[View the full topic](https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784)._