Portainer connecting to some existing container

macom · 7. Februar 2021

Zitat von Nefertiti

Sorry again I did /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker
instead of

/srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker

is correct, filesystems have their mountpoints in the folder /srv/

Nefertiti · 7. Februar 2021

Code

root@rockpro64:~# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker"

but in this case portainer cannot be reached

macom · 7. Februar 2021

You have two disks, right. Make sure to use the right UUID of the disk where the data are.

Make sure there is no typo in the UUID

Nefertiti · 7. Februar 2021

Code

root@rockpro64:~# docker ps
CONTAINER ID   IMAGE                                  COMMAND                  CREATED         STATUS         PORTS                                        NAMES
469bce28eb4f   selfhostedpro/yacht                    "/init"                  20 hours ago    Up 4 minutes   0.0.0.0:8001->8000/tcp                       yacht
5dbd24e1d6fe   linuxserver/airsonic:arm64v8-latest    "/init"                  2 days ago      Up 4 minutes   0.0.0.0:4040->4040/tcp                       airsonic
59e4454d04e8   linuxserver/swag:arm64v8-latest        "/init"                  3 days ago      Up 4 minutes   0.0.0.0:90->80/tcp, 0.0.0.0:450->443/tcp     letsencrypt
b6b8e26116fa   linuxserver/radarr:latest              "/init"                  3 days ago      Up 4 minutes   0.0.0.0:7878->7878/tcp                       radarr
cf95ad482f31   linuxserver/duckdns:arm64v8-latest     "/init"                  3 days ago      Up 4 minutes                                                duckdns
2b46f4b0a73d   linuxserver/nextcloud:arm64v8-latest   "/init"                  3 days ago      Up 4 minutes   0.0.0.0:8090->80/tcp, 0.0.0.0:444->443/tcp   nextcloud
c0fe6065b675   linuxserver/mariadb:arm64v8-latest     "/init"                  3 days ago      Up 4 minutes   0.0.0.0:3306->3306/tcp                       nextclouddb
79a434b25c49   containrrr/watchtower:latest           "/watchtower"            4 days ago      Up 4 minutes   8080/tcp                                     watchtower
fb908724ffc6   valentinalexeev/rpi-cloudcmd:latest    "/usr/src/app/bin/cl…"   19 months ago   Up 4 minutes   0.0.0.0:8000->8000/tcp                       cloudcommander
root@rockpro64:~#

Alles anzeigen

And now nevertheless Yacht can reach them! but what can I do about portainer?

Nefertiti · 7. Februar 2021

Not completely sure but I think portainer try to use dev-disk-by-label-WD_10TB_1

gderf · 7. Februar 2021

Zitat von Nefertiti

Not completely sure but I think portainer try to use dev-disk-by-label-WD_10TB_1

What in Portainer's configuration makes you say that?

Is /dev-disk-by-label-WD_10TB_1 empty?

Nefertiti · 7. Februar 2021

Also can we still use the container from a previous install since all the volumes are still dev-disk-by-label and no dev-disk-by-uuid?

Nefertiti · 7. Februar 2021

Zitat von gderf

What in Portainer's configuration makes you say that?

Is /dev-disk-by-label-WD_10TB_1 empty?

But I think they do come from yesterday and may be I can delete them

And yet portainer installed today at 9:51 is listed in Yacht

Nefertiti · 7. Februar 2021

Into the logs I got errors about dockers? And my duckdns is not working properly since I am getting welcome to swag!

gderf · 7. Februar 2021

Zitat von Nefertiti
Code
root@rockpro64:~# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker"
but in this case portainer cannot be reached

If this is the entire contents of that file it is corrupt.

Nefertiti · 7. Februar 2021

Zitat von gderf

If this is the entire contents of that file it is corrupt.

Well I keep reinstalling Portainer and got the same result.

Portainer is empty in yacht

gderf · 7. Februar 2021

Zitat von Nefertiti

Well I keep reinstalling Portainer and got the same result.

Either the file is incomplete or it is complete and you are not posting the entire contents of it. Which is it?

Nefertiti · 7. Februar 2021

Is somebody can confirm, do I need to change the volume in letsencryt to UUID to have it working again?

Nefertiti · 7. Februar 2021

For some reasons portainer does not want to start.

Nefertiti · 7. Februar 2021

Wondering if it is related cockpit does not install Reason DNS Error?

EDIT

this was fixed but cockpit shows no application

Nefertiti · 8. Februar 2021

Something new "

Code

Something went wrong trying to pull and start portainer "

Code

Docker storage :: /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker
Agent port:: 8000
Web port:: 9000
Yacht port:: 8001
arch   :: arm64
option :: portainer
state  :: install
extras :: 5.4.5
DNS OK.
Removing portainer ...
portainer
Removing portainer/portainer-ce image ...
Untagged: portainer/portainer-ce:latest
Untagged: portainer/portainer-ce@sha256:5064d8414091c175c55ef6f8744da1210819388c2136273b4607a629b7d93358
Deleted: sha256:2e772d0e71cec54f0edf43cb1cd49d33e997d79624e3ff6b49a61a61c09c2a19
Deleted: sha256:2934d31fec9ea9b22252a479b0329146c12fe803b5291a0def264b49abee7b4f
Deleted: sha256:8fbc9bbdaab41b7d76fd793a2aefad137636a493fa65c04aa31cda56b3f04895
Deleted: sha256:8dfce63a73970a18bcc2ca447d9c252aedd3157e9ee02a88e66c53571279aee9
Pulling and starting portainer/portainer-ce ...
d769f7593cdc66d6cc9bbf02c870a87bf7cb81d009cf7b8d8771b579ca1c0db9
Something went wrong trying to pull and start portainer ...
Done.

Alles anzeigen

Code

root@rockpro64:~# docker pull portainer/portainer-ce
Using default tag: latest
latest: Pulling from portainer/portainer-ce
Digest: sha256:5064d8414091c175c55ef6f8744da1210819388c2136273b4607a629b7d93358
Status: Image is up to date for portainer/portainer-ce:latest
docker.io/portainer/portainer-ce:latest

Nefertiti · 9. Februar 2021

Finally my problem was one of my existing docker was using port 8000 I disable it, and portainer was working but still major issues with letsencrypt So i decided to forget about mixing dev-disk-by-uuid and my volume from my container being with dev-disk-by-label

Fortunately I had an old backup image 5.5.5.0.1 So I went from that I did my NFS shares does was working but no letsencrypt /duckdns was not up until by miracle I upgraded to 5.5.23 .(usul)

So far everything is working the reason I did all this, because my rockpro was using ayufan firmware witch did not get any update for a long time.

Jetzt mitmachen!