argg...port 9443 already in use
Just change the host port (the number before the colon) to something else -- or you could just go with http access only on port 9000, and delete the -p 9443:9443 part altogether -- that's for https access.
it appears the ugreen itself is using 9443 for its web portal. i took it out.
the contain spun up, but it doesnt seem to want to connect on 9000
log says 9000 bound without error
im giving up for tonight, ill tackle this again in the morning...
log says portainer timed out.
They say you learn more from your failures than your successes. Ive learned a lot tonight.
lol
When you tackle this again in the morning, you might need to stop and start the Portainer container again -- they only give you so much time to access the WebUI the first time to setup your password:
docker stop portainer
docker start portainer
Then pull up the WebUI promptly to set your password.
Yes, the log said that. I tried to connect on 9000 several times. I did stop and restart per the log.
Ive tried installing it several way, on several different ports (8000, and 9000 seem to be the most common) but it wont let me into the ui. The log says the webservers are active on the correct ports. it keeps timing out.
it doesnt seem to want to install into my docker directory where all my other containers are. i don't know where its actually going as there isn't anything in any of my shares. i assume this is the root of the problem.
The instructions in this step-by-step for installing Portainer on a Ugreen NAS (which is what you're doing right?) look reasonable. I'd suggest giving this a try:
Be sure to stop and remove whatever you've done so far via ssh, before going this route.
i havent tried that one yet, so ill do so.
ive tried about half a dozen others.
following those instructions bombed out.
i did finally get a UI from just using the app to create a new container but now it wont let me add a user.
and now restarting the container, i cant get the ui back...
Portainer is really just another container. One has to wonder how/why Ugreen would want to get in the way of that. Hopefully this won't be a trend with using container-based projects on this NAS.
it hasnt been so far.
tailscale, channels, fastchannels, and jellyfin all installed fine in docker.
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.
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.
What do you mean by bombing out? Are you seeing an error message, and if so, what is it?
it just spit out a bunch of errors in the log and shut down. i didnt keep the container so i cant be specific.
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.
A little background for you on host mode risks:
1 Like
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.