k01e

You're right with the issue regarding to the app, but I think you can mitigate it with a change to the template or a new one. I think the template as is doesn't suit all of our needs. I was looking at ich777's old template and you can setup the template to default to host or bridge and can add the port mapping to the template. When I initially did it, I ran I updated the docker run command and ran it in the Unraid CLI. I think what I would do in the future is use the "Add Container" feature and build the template with the parameters in there. I never really dug into the "Add Container" feature until late last night. I'm just now digging in deeper into all of this. So this might be table stakes or new knowledge like it is to me.

With Photoprism, I was having the same issue as everyone here where I couldn't launch the container with the network in bridge mode and had to use host mode. I'm not a docker expert by any means so I was googling for answers why you can't connected to a container that's in bridge mode and looking for steps to troubleshoot that. That led me to look at the docker run command and when I set the network to bridge (or something other than host) I noticed that the -p parameter is pointing at port 2343 and the default for photoprism is 2342. I copied the run command and changed the parameter to be "-p 2342:2342" and it worked! What it looks like is when the container is using the host network it's not having to "port forward" from the host's port to the port on the container and having the container in bridge mode it relies on that parameter and if it's pointing to the wrong port then it won't work. That's my uneducated thoughts on it anyway. I'm going to see if I can create a bug in github and get it fixed (once I find where it pulls the info to build the docker run command from).