Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace custom nginx image with bind mount #2279

Open
SebastianRzk opened this issue Aug 18, 2024 · 8 comments · May be fixed by #2278
Open

Replace custom nginx image with bind mount #2279

SebastianRzk opened this issue Aug 18, 2024 · 8 comments · May be fixed by #2278
Labels

Comments

@SebastianRzk
Copy link

Why?

The image does not need to be built (why should it?)
Fewer files and less code = easier maintenance and fewer potential bugs
the container can be easily updated (for example via a program like watchtower)

Pull-Request: #2278

@joshtrichards joshtrichards linked a pull request Aug 18, 2024 that will close this issue
@joshtrichards
Copy link
Member

#538 (comment)

and #559

for some historical context.

@peschmae
Copy link

I think this would be a great time to also switch to the official unprivileged nginx image, as root isn't required if the ports are mapped anyways.

This would require to change the nginx pid file and the listen port, but the rest could remain the same.

@SebastianRzk
Copy link
Author

@joshtrichards oh, I didn't know about that.

Yeah, docker on windows is still some sort of mystery. Sadly, I can not test this :/

Thanks for the information.

@SebastianRzk
Copy link
Author

@peschmae yes, that's another good idea (that can be implemented independent from this improvement).

Since the nginx-proxy autodetects the port, the change in the yml file should be minimal to none. To be safe, you can add the VIRTUAL_PORT env variable to the web service.

@joshtrichards
Copy link
Member

It's possible it's handled better under Docker for Windows these days. It's been years since I used Docker on Windows. Unfortunately, I don't have an online Windows workstation handy to test on at the moment.

If someone is able to test a bit on a current setup and report back that would be informative.

@tzerber
Copy link
Contributor

tzerber commented Sep 24, 2024

Nowadays Docker for Windows uses WSL2. WSL2 is de-facto linux distro running inside Windows and all the tests I do on docker containers i do them in WSL2, without any problems in the past >2 years.

I am unsure on how the image will work on WS2022 + HyperV but I will try it in the next days to see how it behaves on Hyper-V hosts. Docker docs claims there's no difference between HyperV and WSL2.

The only case that I see de-facto untestable is Docker Business + VMware ESXi and I'm pretty sure if there's someone with that combo, he can just run a Linux-based VM with docker inside.

@joshtrichards
Copy link
Member

WSL2

Yeah I semi-suspected as much. It'd certainly be great if we could clean this up and still work for >80% of use cases out there.

@tzerber
Copy link
Contributor

tzerber commented Sep 24, 2024

Just tested on a virtual Windows Server 2022 Datacenter, it uses WSL2 too, so no problems there. I can't enable Hyper-V due hypervisor limitations, probably someone running VMWare hypervisor see this and test it ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants