Having trouble setting up Portainer on a Ugreen NAS

Hosting Containers
#21

the reality is the ugreen docker app allows in-place image/container upgrades so im not sure what use portainer would be to me.

i have a feeling the initial registration timeout is too short for the web servers to spin up and i just got lucky that one time.

is there someway to change/disable that timeout? i know its a security feature, but it doesnt seem to be useful here.

also, this is the only bridged container out of the 5, so i wonder if thats part of the issue.

i tried creating the container in host mode, but it kepped bombing out.

#22

As a general rule, you don't want to use host mode for containers, as isolation is one of the benefits of Docker. Yes, there are a few projects that require it, but you definitely don't want to use it by default.

#23

What do you mean by bombing out? Are you seeing an error message, and if so, what is it?

#24

it just spit out a bunch of errors in the log and shut down. i didnt keep the container so i cant be specific.

#25

i dont need the isolation on a NAS, so host mode is fine for me.

im going to try to copy over the data directory from my windows portainer and see if that does anything.

#26

A little background for you on host mode risks:

1 Like
#27

good stuff there

I will endeavor to be careful and not use host mode for projects im unfamiliar with.

i am new to docker so the heads up is appreciated.