How to access portainer?

I suggest you check out their docs: Overview - Auckland, Singapore, San Francisco | Portainer.io

Hi there,

If I'm allowed to pick up an old thread, I'm also stuck on this issue. I am very new to docker and can't find a way to use portainer. Here is the log:

-- Journal begins at Wed 2022-01-26 06:55:27 WET. --
Jan 26 10:44:25 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:29 LibreELEC sh[59756]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:39 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 1.
Jan 26 10:44:39 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:39 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:42 LibreELEC sh[59809]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:52 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 2.
Jan 26 10:44:52 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:52 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:54 LibreELEC sh[59865]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 3.
Jan 26 10:45:05 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Start request repeated too quickly.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: Failed to start docker.linuxserver.portainer container.

I have no idea what the lsio network is...

Quote from darav

Hi there,

If I'm allowed to pick up an old thread, I'm also stuck on this issue. I am very new to docker and can't find a way to use portainer. Here is the log:

Code

-- Journal begins at Wed 2022-01-26 06:55:27 WET. --
Jan 26 10:44:25 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:29 LibreELEC sh[59756]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:39 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 1.
Jan 26 10:44:39 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:39 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:42 LibreELEC sh[59809]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:52 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 2.
Jan 26 10:44:52 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:52 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:54 LibreELEC sh[59865]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 3.
Jan 26 10:45:05 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Start request repeated too quickly.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: Failed to start docker.linuxserver.portainer container.

Display More

I have no idea what the lsio network is...

lsio is the custom docker network set up by the updater addon, which is a dependency for all the docker addons in the linuxserver repo.

No idea why it says it doesn't exist. Try disabling and re-enabling the updater addon and check its log

Quote from darav

... I am very new to docker and can't find a way to use portainer ...

Sorry, I've done a lot of portainer installations and never had a problem.

• If you have problems start with a clean installation of Docker first and Portainer second. To do this uninstall both, remove any trace of the directories /storage/.kodi/userdata/addon_data/service.system.docker and Portainer (whose name I don't remember because I don't use the installation addon of this addon).
• Reboot the device.
• Install Docker again and reboot the device.
• Install Portainer again and reboot the device.
• Create a username and password for Portainer on the web http://<device-ip>:9000
• Explore the contents of Portainer: I use it to manage other installed containers: stop, start, delete containers and docker images, also to explore linux commands inside containers, delete volumes, ..., in relation to networks I don't need use this for nothing. Instead of using docker volumes I always mount the external storage containers in /storage/.config/dockers, /storage, and /media of LibreELEC.

Thanks for the help.

I have uninstalled and reinstalled portainer first (before removing docker completely...).

The log is a bit different:

-- Journal begins at Sat 2022-01-29 16:26:30 WET, ends at Sat 2022-01-29 18:25:39 WET. --
Jan 29 16:26:41 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 29 16:26:42 LibreELEC sh[946]: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 16:26:42 LibreELEC sh[966]: docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
Jan 29 16:26:42 LibreELEC sh[966]: See 'docker run --help'.
Jan 29 16:26:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 29 16:26:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 29 16:26:52 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 1.
Jan 29 16:26:52 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 29 16:26:52 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 29 16:27:09 LibreELEC sh[1306]: docker: Error response from daemon: network lsio not found.
Jan 29 16:27:09 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 29 16:27:09 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 29 16:27:19 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 2.
Jan 29 16:27:19 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 29 16:27:19 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 29 16:27:22 LibreELEC sh[1710]: docker: Error response from daemon: network lsio not found.
Jan 29 16:27:22 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 29 16:27:22 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 29 16:27:32 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 3.
Jan 29 16:27:32 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 29 16:27:32 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Start request repeated too quickly.
Jan 29 16:27:32 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 29 16:27:32 LibreELEC systemd[1]: Failed to start docker.linuxserver.portainer container.

Would you still recommend scrubbing docker + portainer?

PS: I've tried another solution from the forum that has worked nicely for me. I've set up portainer directly:

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

Works fine after restarting kodi!

Hi there,

seems there is another issue

Quote

Code

journalctl -u docker.linuxserver.portainer -f

logs

FTL github.com/portainer/portainer/api/cmd/portainer/main.go:730 > failed initializing upgrade service | error="failed to determine container platform: failed to retrieve docker info: Error response from daemon: client version 1.41 is too new. Maximum supported API version is 1.40" stack_trace=[{"func":"NewService","line":"55","source":"upgrade.go"},{"func":"buildServer","line":"728","source":"main.go"},{"func":"main","line":"801","source":"main.go"},{"func":"main","line":"250","source":"proc.go"},{"func":"goexit","line":"831","source":"asm_arm.s"}]

anyone else having the same issue?

Seems to pretty new portainer-ce crashing, will not start · Issue #8455 · portainer/portainer (github.com)

Quote from darav

PS: I've tried another solution from the forum that has worked nicely for me. I've set up portainer directly:

Code

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

Works fine after restarting kodi!

Hello, I'm having the same problem when installing Portainer. I tried this manual installation and it presents me with this message.

Could you help me?

Unable to find image 'portainer/portainer-ce:latest' locally
docker: Error response from daemon: Head "https://registry-1.docker.io/v2/portainer/portainer-ce/manifests/latest": dial tcp: lookup registry-1.docker.io on 192.168.25.1:53: no such host.
See 'docker run --help'.

I would say it can not reach docker hub

Does it work with other images / container?

Quote from PackElend

I would say it can not reach docker hub

Does it work with other images / container?

No, my docker is empty. I'm only needing the portainer to be able to use Medusa and Transmission.

I used the portainer in Raspiberry 4 but as it malfunctioned, now I'm configuring everything on a PC with libreelec.