Generic Docker "installation" in README

[Yrlish]

Hi,

I want to suggest adding these steps in the README for "installation" (this is more like usage really), because I didn't want to install PowerShell in my Linux-distro, has no Windows machine and have Docker available.

1. Start PowerShell container: docker run --interactive --tty mcr.microsoft.com/powershell:latest
2. Inside container: Invoke-WebRequest -Uri https://github.com/bryanroscoe/shield_optimizer/raw/refs/heads/main/Shield-Optimizer.ps1 -OutFile Shield-Optimizer.ps1
3. Run ./Shield-Optimizer.ps1
4. Connect via auto discovery or manually with IP

I had to connect manually, doesn't know if that's because auto discovery didn't work inside docker or if it's my network. Other than that, this utility tool worked perfectly!

I don't know too much of PowerShell, maybe there is a better one-liner for the docker run command, doing everything; starting container, download the script and executing it.

[bryanroscoe]

Yeah there is an issue with subnet detection and docker for the auto discovery to work and I have not had a chance to work out the kinks. I actually have a dockerfile in the repo to verifying it works on linux.

Running this in docker is a much heavier lift than just installing powershell on linux. PowerShell is an open source multiplatform software no real downside to installing it, https://github.com/PowerShell/PowerShell

If I get some time I will play around with getting the networking working in docker.

[Yrlish]

PowerShell may sure be useful in some circumstances, but for me I felt it being too much and unnecessary to install PowerShell just to run this script, especially when you can simply run it in an interactive docker container. I'm sure others are feeling the same.

The official PowerShell container I refered to looked pretty tiny, maybe you look into basing your own dockerfile of that instead of Ubuntu that is quite much larger.

If you already have docker installed in your system I wouldn't say using it is a heavier lift than installing PowerShell. After using the container it's much easier and faster to trash everything with a clean command.

[bryanroscoe]

The most recent mcr.microsoft.com/powershell is not stable on mac which most of the users are using.

Docker is a much heavier dependency for the average person, and networking is tricker.

[shawly]

Yeah there is an issue with subnet detection and docker for the auto discovery to work and I have not had a chance to work out the kinks. I actually have a dockerfile in the repo to verifying it works on linux.

Just using --network host is enough to make it work. I used the mcr.microsoft.com/powershell:latest image and installed the iproute2 package and autodiscovery works just fine.