Error while installing on brand new raspberry pi 4 bullseye

[HamzaSheikh1234]

Whenever I try running the ansible playbook, I always get the same error while it installs.

Here's the output:

PLAY [internet_pi] **** TASK [Gathering Facts] ok: [127.0.0.1]

TASK [Load configuration (with defaults from example file).] ***ok: [127.0.0.1] => (item=example.config.yml) ok: [127.0.0.1] => (item=config.yml)

TASK [Ensure apt cache is up to date.] *****ok: [127.0.0.1]

TASK [Ensure pacman cache is up to date] ***skipping: [127.0.0.1]

TASK [Check if Docker is already present.] *****ok: [127.0.0.1]

TASK [Download Docker install convenience script.] *****skipping: [127.0.0.1]

TASK [Run Docker install convenience script.] **skipping: [127.0.0.1]

TASK [Ensure Docker is started.] ***ok: [127.0.0.1]

TASK [Ensure dependencies are installed (Debian).] *****ok: [127.0.0.1]

TASK [Ensure dependencies are installed (Archlinux).] **skipping: [127.0.0.1]

TASK [Install Docker Compose using Pip.] ***ok: [127.0.0.1]

TASK [Ensure user is added to the docker group: pi] ****ok: [127.0.0.1]

TASK [Reset connection so docker group is picked up.] **[WARNING]: Reset is not implemented for this connection

TASK [Gather package facts.] ***skipping: [127.0.0.1]

TASK [Add Buster backports apt key.] ***skipping: [127.0.0.1] => (item=04EE7237B7D453EC) skipping: [127.0.0.1] => (item=648ACFD622F3D138) skipping: [127.0.0.1]

TASK [Add Buster backports for fixed libseccomp2.] *****skipping: [127.0.0.1]

TASK [Install >libseccomp2.4.4 to fix 32-bit OS issue.] ****skipping: [127.0.0.1]

TASK [Synchronize internet-monitoring directory.] **ok: [127.0.0.1]

TASK [Ensure internet-monitoring directory is not a Git repository.] ***ok: [127.0.0.1]

TASK [Copy templated internet-monitoring files into place.] ****ok: [127.0.0.1] => (item={'src': 'docker-compose.yml.j2', 'dest': 'docker-compose.yml'}) ok: [127.0.0.1] => (item={'src': 'grafana-config.monitoring.j2', 'dest': 'grafana/config.monitoring'}) ok: [127.0.0.1] => (item={'src': 'prometheus.yml.j2', 'dest': 'prometheus/prometheus.yml'}) ok: [127.0.0.1] => (item={'src': 'prometheus-pinghosts.yaml.j2', 'dest': 'prometheus/pinghosts.yaml'})

TASK [Ensure internet-monitoring environment is running.] ** fatal: [127.0.0.1]: FAILED! => {"changed": false, "errors": [], "module_stderr": "", "module_stdout": "latest: Pulling from grafana/grafana\n", "msg": "Error starting project Get \"https://registry-1.docker.io/v2/grafana/grafana/manifests/sha256:87088a71e59db63089914424355976b02594c02d6e78a607f1524fe863d69510\": dial tcp: lookup registry-1.docker.io on [2606:4700:4700::1001]:53: dial udp [2606:4700:4700::1001]:53: connect: network is unreachable"}

PLAY RECAP ***** 127.0.0.1 : ok=11 changed=0 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0

[geerlingguy]

It seems like Docker is not able to pull a container. Is the Pi getting network traffic? Can you curl registry-1.docker.io or ping it? Can you ping other sites? Maybe that registry URL is blocked on your network?

[HamzaSheikh1234]

It seems like Docker is not able to pull a container. Is the Pi getting network traffic? Can you curl registry-1.docker.io or ping it? Can you ping other sites? Maybe that registry URL is blocked on your network?

I can curl and ping other sites, yet for some reason I don't get a response from the registry site.

[iammac2]

I have the same issue. curl and ping both ok.

Any update?

[iammac2]

This fixed it for me - although it's probably not a great move from a security perspective

sudo chmod 666 /var/run/docker.sock

[HamzaSheikh1234]

I have the same issue. curl and ping both ok.

Any update?

I tried it on my other pi running the 32-bit OS and it worked perfectly fine.

[FronchToast]

This fixed it for me - although it's probably not a great move from a security perspective

sudo chmod 666 /var/run/docker.sock

I did this as well and it got me past the error I was seeing, things are working fine now. Clearly some kind of (implicit or explicit) permission prerequisite that I missed.

[shaperilio]

If it's a permissions thing, maybe try this?

[github-actions[bot]]

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[bot]]

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.