# 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:** 3

<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, 6:35pm UTC](https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784/3 "2023-02-13T18:35:53Z")

</div>

If you also need these capabilities (for sub-1024 port binding as non-root user and raw socket use for ICMP, respectively), yes, you'd specify those in your container config.

refs:

- [Docker run reference | Docker Documentation](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)
- [compose-spec/spec.md at master · compose-spec/compose-spec · GitHub](https://github.com/compose-spec/compose-spec/blob/master/spec.md#cap_add)

---

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