@GitGab19 identified a limitation on our side: we currently rely on Docker IPC communication to manage some containers, but this approach is not compatible with the Umbrel environment.
After discussing the issue with people on the Umbrel Discord, the conclusion was that Docker-in-Docker (DinD) is likely the best approach for this scenario.
This issue aims to investigate that possibility and adapt our application where necessary.
Another important question is whether Docker-in-Docker can fully replace our current setup, including for users outside the Umbrel platform. If not, we may need to maintain both approaches, which would add complexity and is probably not ideal long term.
Also, this could be an effort to mitigate the security implications raised by #134
for reference:
#131 (comment)
@GitGab19 identified a limitation on our side: we currently rely on Docker IPC communication to manage some containers, but this approach is not compatible with the Umbrel environment.
After discussing the issue with people on the Umbrel Discord, the conclusion was that Docker-in-Docker (DinD) is likely the best approach for this scenario.
This issue aims to investigate that possibility and adapt our application where necessary.
Another important question is whether Docker-in-Docker can fully replace our current setup, including for users outside the Umbrel platform. If not, we may need to maintain both approaches, which would add complexity and is probably not ideal long term.
Also, this could be an effort to mitigate the security implications raised by #134
for reference:
#131 (comment)