Non-Docker Version

[TransRapid]

Idea

Docker adds an unnecessary layer of overhead and forwarding. Is there a reason why there is no option to list dependancies and go from there? It is far more work to have to deal with Docker than it is to just manage dependencies that are already installed, and have things be able to easily communicate with each other.

If it isn't clear, the goal is to install this without the extra layer and management of docker, which is by any means not less work to manage.

[bohemtucsok]

Hello It only works if you put the container in a host mod because you don't use the usual IP so I need an iptables forward rule, I use it and it works perfectly.

[TransRapid]

Hello It only works if you put the container in a host mod because you don't use the usual IP so I need an iptables forward rule, I use it and it works perfectly.

I'm not sure if there was some bit of translation done here but this doesn't entirely make sense grammatically; or something is missing.

Really confused on what is being said here, especially about what you need. If it was translated maybe put the original language and I'll try to translate it from there and see what I can make of it.

What do you mean by "usual IP"? Are you referring to the assigned or static IP of the device this is running on?

Also, what works perfectly?

[bohemtucsok]

since the container, as you wrote, does not use the basic port 80 443, an iptables rule must be written, and yes, you will only be able to see the real ip in host mode

[TransRapid]

I understand that, but still not sure why this has to be installed within a docker container. The official page or documented cause is due to dependencies, but I would rather manage those. Then have to have a virtualized environment.

It doesn't logically make any sense to run a virtual environment to manage a service installed on the host, and far more work to configure such networking in that type of setup.

The other issue is that you end up wasting resources when you have multiple copies of the same packages running, and it just comes down to lazier management at a certain point when more things than not rely on the same libraries-all of which you want to have on the latest version possible for security reasons especially. If you don't care about security and just want things to work, and don't really care to understand what you are installing, it is fine, but if you want to do things the most efficient way possible, it doesn't make sense to do something like this in docker, especially as it is being depreciated as a platform overall.

I don't update or upgrade everything right away, but I keep it up to date, and within reason after a certain point I will find other ways to accomplish a task if a tool becomes non-compliant because it can't run current updates or security patches.

The next thing maybe is just to look at the docker image and break it down to natively install it. I did that with Scrypted, and it was exponentially faster and more reliable, especially when it came to native video encoding.

[TransRapid]

The fact that this is so open is what makes it great though, someone can put a lot of work and make a docker image that for me is more proof of concept, and then I can go and break it down to make it fit my needs.

I'll share what I end up doing.

[jlesage]

It's not just a question of dependencies. If you look at the software itself (https://github.com/NginxProxyManager/nginx-proxy-manager), you will see that it is tightly linked with its environment. Docker allows to control this environment and ease usage and deployment of the software for most people.

Note that the main audience of this project is people that want an easy-to-use solution at home. Advanced people will likely manually configure Nginx themself, without requiring a nice UI to do it.

[TransRapid]

I just started to look at your docker image to get a better idea. 8 wasn't sure if there was anything in particular that was an outright reason why it was run in docker for something more obscure. Thanks for the work you've put into this project btw.