Fresh install of internet-pi on latest stable Raspbian fails to create all required docker components

[winzlocom]

Error received during installation process:
TASK [Ensure internet-monitoring environment is running.] **********************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "errors": [], "module_stderr": "", "module_stdout": "", "msg": "Error starting project 500 Server Error for http+docker://localhost/v1.41/images/prom/prometheus:v2.25.2/json: Internal Server Error ("stat /var/lib/docker/overlay2/58e1ca758ffe7cfaf28425fc8608fa1181b4766f5e1303901ce3c35151eea1d3: no such file or directory")"}

I have already backed the bcrypt library back to the release prior to 4.0.0 per another bug's comments and that got me further, but I cannot get past this step no matter how I manipulate config.yml, including leaving everything as-is from the example-concif.yml file.

I had this working yesterday and decided to get bold and update it to the latest version. Tried removing all docker containers/volumes/networks/images, uninstalling/reinstalling docker, python3-pip and sensible with no luck. Still using the same user account that I used prior and my inventory.ini file is unchanged from how it was prior to my update attempt.

Any ideas? I've been at this for over 8 hours now with no luck. From the look of it, there are no actual Docker containers running if I execute 'docker container list', and if I go into the 3 directories that reside under '~/internet-monitoring', I see only 3 active containers while executing 'docker-compose ps', if I'm lucky, I can see active processes running on post 9090 9115 and 9798. However, at this time after another clean wipe of the environment, I have nothing coming up under those 3 directories.

[winzlocom]

Today I got bold, removed docker-ce and wmdocker from my apt repository, wiped everything in /var/lib/docker, and /var/run/docker* and repeated the process from HEAD of the repository. Same failure point, different error:

TASK [Ensure internet-monitoring environment is running.] **********************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "errors": ["ERROR: for internet-monitoring_nginx-proxy_1 Cannot start service nginx-proxy: driver failed programming external connectivity on endpoint internet-monitoring_nginx-proxy_1 (3f268ecb3e7c8eabfea06e3ea78341979fc5fbfcf5df24723b92373a40cabd28): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use"], "module_stderr": "Creating internet-monitoring_nodeexp_1 ... \nCreating internet-monitoring_ping_1 ... \nCreating internet-monitoring_speedtest_1 ... \nCreating internet-monitoring_nginx-proxy_1 ... \nHost is already in use by another container\nCreating internet-monitoring_nginx-proxy_1 ... error\n\nERROR: for internet-monitoring_nginx-proxy_1 Cannot start service nginx-proxy: driver failed programming external connectivity on endpoint internet-monitoring_nginx-proxy_1 (3f268ecb3e7c8eabfea06e3ea78341979fc5fbfcf5df24723b92373a40cabd28): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use\nCreating internet-monitoring_nodeexp_1 ... done\nCreating internet-monitoring_ping_1 ... done\nCreating internet-monitoring_speedtest_1 ... done\n", "module_stdout": "latest: Pulling from nginxproxy/nginx-proxy\nDigest: sha256:00f6557f4bba60c2a0d7fce44f2a92e284d761c2a5a302a46b634ee48d0682c1\nStatus: Downloaded newer image for nginxproxy/nginx-proxy:latest\nlatest: Pulling from grafana/grafana\nDigest: sha256:129d050943ae2d9c473191c0b573a2e53facce6f7808c5d48f1a66d424c4e81b\nStatus: Downloaded newer image for grafana/grafana:latest\nlatest: Pulling from prom/blackbox-exporter\nDigest: sha256:608acee5704ad49c3308b900230dfc00b25da0c90425f8fed55cf005e07f521b\nStatus: Downloaded newer image for prom/blackbox-exporter:latest\nlatest: Pulling from miguelndecarvalho/speedtest-exporter\nDigest: sha256:2e5f1e38180be50afe87eb038039efb22c1f75ba8c131f1a9c2eabaaf9d2a207\nStatus: Downloaded newer image for miguelndecarvalho/speedtest-exporter:latest\nv2.25.2: Pulling from prom/prometheus\nDigest: sha256:c24ab4ef6187de7e79c4578e6fccb22cb73b8da662987328a828a65410fe6ae9\nStatus: Downloaded newer image for prom/prometheus:v2.25.2\nlatest: Pulling from prom/node-exporter\nDigest: sha256:4dc469c325388dee18dd0a9e53ea30194abed43abc6330d4ffd6d451727ba3e6\nStatus: Downloaded newer image for prom/node-exporter:latest\n", "msg": "Error starting project Encountered errors while bringing up the project."}

I'm really stuck on this one, guys. The only thing I did for maintenance on the PI was an apt update/upgrade, and to replace my clone of the repository with a fresh one from GitHub. I've followed the README.rd file's installation steps to ensure my process is consistent between attempts, and the only thing varying now is what is pre-loaded into Raspbian 11.5 (it is the 32-bit version), and the tag I've changed from 3.2.1, to 3.2.0 and to 3.1.0 with no differences.

This gives me the feeling like something is being missed in dependency checks/resolutions, or pre-install documentation, as I got this going a couple of years ago with next to no issues, and this time it's pushing back hard.

[geerlingguy]

Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use

That indicates something else is already running on port 80 on the Pi. Maybe you have Apache or Nginx or Caddy running on the Pi? You can check with netstat -tulpn | grep :80

[winzlocom]

You nailed it, rogue apache2 instance got started from some part of the apt package upgrade process. Once I stopped/disabled it, everything worked like a charm. Consider this closed, with overly-verbose debug information and my visual impairment being the cause for not catching such a simple oversight on my own.

…

On Nov 3, 2022, at 9:47 AM, Jeff Geerling ***@***.***> wrote: Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use That indicates something else is already running on port 80 on the Pi. Maybe you have Apache or Nginx or Caddy running on the Pi? You can check with netstat -tulpn | grep :80 — Reply to this email directly, view it on GitHub <#459 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWMJQ4JQEPEW2X4DNEGSVYTWGPGABANCNFSM6AAAAAARTYIMY4>. You are receiving this because you authored the thread.

[stale]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[github-actions]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[github-actions]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.