New installation of Dietpi, Docker and Portainer with errors. Here is the LOG from Portainer:
level=info msg="2022/02/22 13:53:13 [FATAL] [internal,init] No administrator account was created in 5.000000 mins. Shutting down the Portainer instance for security reasons"
INFO 2022/02/22 13:53:15 Encryption key file `portainer` not present
INFO 2022/02/22 13:53:15 Proceeding without encryption key
INFO 2022/02/22 13:53:15 Loading PortainerDB: portainer.db
INFO 2022/02/22 13:53:15 Opened existing store
level=info msg="2022/02/22 13:53:15 [INFO] [main,compose] [message: binary is missing, falling-back to compose plugin] [error: docker-compose binary not found]"
2022/02/22 13:53:15 server: Reverse tunnelling enabled
2022/02/22 13:53:15 server: Fingerprint 25:1f:3c:bc:47:1f:ec:13:57:f6:36:86:dc:08:a4:90
2022/02/22 13:53:15 server: Listening on 0.0.0.0:8000...
INFO 2022/02/22 13:53:15 [INFO] [cmd,main] Starting Portainer version 2.11.1
level=info msg="2022/02/22 13:53:15 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"
level=info msg="2022/02/22 13:53:15 [DEBUG] [internal,init] [message: start initialization monitor ]"
level=info msg="2022/02/22 13:53:15 [INFO] [http,server] [message: starting HTTP server on port :9000]"
level=info msg="2022/02/22 13:53:15 [INFO] [http,server] [message: starting HTTPS server on port :9443]"
level=info msg="2022/02/22 13:55:57 http error: No administrator account found inside the database (err=object not found inside the database) (code=404)"
level=info msg="2022/02/22 13:55:57 http error: No administrator account found inside the database (err=object not found inside the database) (code=404)"
level=info msg="2022/02/22 13:56:11 http error: Unable to initiate communications with environment (err=unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined) (code=500)"
Raspi PI 4 Dietpi v8.1.2. …
103 DietPi-RAMlog: Makes /var/log a RAM disk, preserves file structure on reboot
│ [ ] 104 Dropbear: Lightweight SSH server
│ [ ] 130 Python 3: Runtime system, pip package installer and development headers
│ [ ] 134 Docker Compose: Manage multi-container Docker applications
│ [ ] 162 Docker: Build, ship, and run distributed applications
│ [ ] 185 Portainer: Simplifies container management in Docker (standalone host)
│ [ ] 200 DietPi-Dashboard (beta): Official lightweight DietPi web interface (Rust)
Did you tried to reinstall the container. There is no DietPi magic behind. We simply start the container. Probably it need to be reported upstream if there is an issue on the container itself.
Same here. Brand new installation. Only OpenSSH, Docker installed before installing Portainer. v8.14 x86 PC VMware BIOS or UEFI. Always the same no matter how many times I tried in the past week.
┌─────────────────────────────────────────┤ DietPi-Software ├─────────────────────────────────────────┐
│ - Command: docker run -d -p 9002:9000 --name=portainer --restart=always -v │
│ /run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce │
│ - Exit code: 125 │
│ - DietPi version: v8.14.2 (MichaIng/master) | HW_MODEL: 21 | HW_ARCH: 10 | DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: from scratch │
│ - Error log: │
│ Unable to find image 'portainer/portainer-ce:latest' locally │
│ docker: Error response from daemon: Get │
│ "https://registry-1.docker.io/v2/portainer/portainer-ce/manifests/sha256:9fa1ec78b4e29d83593cf97206 │
│ 74b72829c9cdc0db7083a962bc30e64e27f64e": dial tcp: lookup registry-1.docker.io on 192.168.1.1:53: │
│ no such host. │
│ │
│ Retry : Re-run the last command that failed │
│ DietPi-Config : Edit network, APT/NTP mirror settings etc │
│ Open subshell : Open a subshell to investigate or solve the issue │
│ Send report : Uploads bugreport containing system info to DietPi │
│ ●─ Devs only ──────────────────────────────────────● │
│ Change command : Adjust and rerun the command │
│ │
│ │
│ <Ok> <Exit> │
│ │
└─────────────────────────────────────────────────────────────────────────────────────────────────────
console output:
Step: Installing Portainer: Simplifies container management in Docker (standalone host)
[ OK ] DietPi-Software | docker volume create portainer_data
[ INFO ] DietPi-Software | Portainer will be deployed now. This could take a while...
[ INFO ] DietPi-Software | docker run -d -p 9002:9000 --name=portainer --restart=always -v /run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce, please wait...
Unable to find image 'portainer/portainer-ce:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/portainer/portainer-ce/manifests/sha256:9fa1ec78b4e29d83593cf9720674b72829c9cdc0db7083a962bc30e64e27f64e": dial tcp: lookup registry-1.docker.io on 192.168.1.1:53: no such host.
See 'docker run --help'.
[FAILED] DietPi-Software | docker run -d -p 9002:9000 --name=portainer --restart=always -v /run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce
[ INFO ] DietPi-Software | docker run -d -p 9002:9000 --name=portainer --restart=always -v /run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce, please wait...
Unable to find image 'portainer/portainer-ce:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/portainer/portainer-ce/manifests/sha256:9fa1ec78b4e29d83593cf9720674b72829c9cdc0db7083a962bc30e64e27f64e": dial tcp: lookup registry-1.docker.io on 192.168.1.1:53: no such host.
See 'docker run --help'.
[FAILED] DietPi-Software | docker run -d -p 9002:9000 --name=portainer --restart=always -v /run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce
[ INFO ] DietPi-BugReport | Generating informative command outputs, please wait...
/boot/dietpi/dietpi-bugreport: line 138: aplay: command not found
/boot/dietpi/dietpi-bugreport: line 138: aplay: command not found
Warning: The unit file, source configuration file or drop-ins of docker.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of docker.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[ INFO ] DietPi-BugReport | cp /tmp/G_EXEC_ERROR_REPORT G_EXEC_ERROR_REPORT, please wait...
[ OK ] DietPi-BugReport | cp /tmp/G_EXEC_ERROR_REPORT G_EXEC_ERROR_REPORT
[ OK ] DietPi-BugReport | Packing upload archive
[ OK ] DietPi-BugReport | Sending bug report
[ OK ] DietPi-BugReport | Your bug report has been successfully uploaded.
- Reference code: 8b6d47d7-097c-4a2b-9a5f-cd5415be7eba
its a Native PC and not an RPi. On x86 Docker has some challenges with missing Apparmor tool. Something Docker guys are aware and hopefully gonna change in future. As workaround you can install Apparmor.
There should be no relation between the issue to start container on x86 and local DNS server tools.
Yep. It’s AppArmor causing the problem. Although I did not see AppArmor error message and the error message always was “dial tcp: lookup registry-1.docker.io on xx.xx.xx.xx:53: │
│ no such host.”
I tried to use different DNS settings (Google, Cloudflare, Pi-Hole, Technitium) or use a real PC yet nothing worked.
apply the following 2 commands at the console then reinstall Portainer and the installation finally went through without error
I deleted the DietPi VM and redid the Docker & Portainer installation
Found that not only I have to install apparmor then disable it, I still have to change default DNS that’s issued by router DHCP (which usually will forward to ISP’s DNS) to one of the public DNS, otherwise the Portainer installation will still fail.
There are tons of name resolution issue postings all over the internet for Docker image pulls for different reasons.
You can install pihole and unbound…then point all your DHCP addresses issued to that machine (wether bare metal or docker)…and it will resolve DNS thru your network…
