# WSL2 & Docker-compose

**URL:** <https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [September 3, 2021, 9:15pm UTC](https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615 "2021-09-03T21:15:02Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [April 2, 2022, 2:52am UTC](https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615/5 "2022-04-02T02:52:28Z")

</div>

> [@kcollins](#):
>
> I’ve went ahead and updated the ticket here on our side with some of the updated thinking on this–hopefully we can get to it sooner vs later. It will likely be opt-in for `inductiveautomation/ignition:8.1.x` (i.e. if you don’t specify anything, it will continue to run as-root like today).

Saw this on another forum post and thought, hmm why does that sound ironically familiar? 😂😂

> [@\[Bug-5368\] Ignition Gateway Service User](https://forum.inductiveautomation.com/t/bug-5368-ignition-gateway-service-user/57914/1):
>
> Our team is following this article:[Ignition Security Hardening Guide | Inductive Automation](https://www.inductiveautomation.com/resources/article/ignition-security-hardening-guide)
> 
> ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/8/0805836ebafe56a6993411065d135dc4370cb848.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615)._