# WSL2 & Docker-compose **URL:** \ **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:** 8
**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:** [April 2, 2022, 3:12am UTC](https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615/8 "2022-04-02T03:12:54Z")
> [@kgamble](#): > > Question, will this back port to versions older than 8.1.17 containers? so that the developers who are stuck on something like 8.1.15 gateways for a while can use this feature as its version agnostic? We won't be back-porting this and rebuilding+pushing older Ignition versions back up to Docker Hub, no. However, once this gets to release, I'd be happy to put together a derived image that can be built against one of those older upstream images to _shim_ in this functionality. It will look very similar to what is mentioned [here](https://forum.inductiveautomation.com/t/specifying-modules-on-gateway-docker-compose/50361/3). > [@kgamble](#): > > Separately, a more linux question, when re-creating a container with this, prior to rebuilding the container should all files in the data folder (or wherever a bind mounted volume may be) be modified for use by the desired group? Currently the rough solution I have been using is a `chmod -R a+rwX directory/path` on the folder being used. In this case we would either want to set the GID to 1000 so it acts as the user, or put the user and the gateway in a common group and perform `chgrp -R group_name directory/path` ? With this new configuration, the entrypoint script still runs as root and will automatically `chown -R` (for the most part, there is some advanced handling built into there for symlinks, too) files under `IGNITION_INSTALL_LOCATION` (including under any bind-mounts or volumes in the tree) to the target `UID:GID` specified. It will not modify permissions, just ownership. --- _[View the full topic](https://forum.inductiveautomation.com/t/wsl2-docker-compose/50615)._