search

pwt / docker-airconnect-arm

Docker builds of AirConnect for Raspberry Pi devices. Optimised for Sonos.
Apache License 2.0
37 stars 8 forks source link

Permission denied / no such container : airconnect #12

Closed ape404 closed 2 years ago

ape404 commented 2 years ago

I have seen your instructions, installed docker successfully but when I start the container with:

pi@RPi:~ $ docker run -d \

--net=host \ --name=airconnect \ --restart=unless-stopped \ -e SUPPRESS_FLUSH=TRUE \ -e INCLUDE_AIRCAST=TRUE \ psychlist/docker-airconnect-arm

I have got the following response:

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=airconnect": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run –help'

I have also tried updating. It seems to process quite a lot of things but it then ended with:

… Digest: sha256:fbde5d10112290dab4318ba0bac3d04c8b503eea1dbfad55cf23c0770a095125 Status: Downloaded newer image for psychlist/docker-airconnect-arm:latest docker.io/psychlist/docker-airconnect-arm:latest Error: No such container: airconnect bash: psychlist/docker-airconnect-arm: No such file or directory

What am I doing wrong here? Thanks a lot for your help.

Albert Peter-Jordi Passwangstrasse 15 4411 Seltisberg Tel. +41 61 911 0744 eMail albert.peter@eblcom.ch

pwt commented 2 years ago

Hi:

Looks like your docker installation isn't set up correctly, because you're getting a generic Docker permission error. Please try:

sudo docker run --rm hello-world

If that succeeds, then your user pi is probably not a member of the docker group. Have you done the following as in the Docker installation instructions?

sudo usermod -aG docker pi

If not, please do so, then start a new shell for it to take effect, and try the airconnect container again.

Finally, as a last resort, start the container as root:

sudo docker run --rm -d \
  --net=host \
  --name=airconnect \
  --restart=unless-stopped \
  -e SUPPRESS_FLUSH=TRUE \
  -e INCLUDE_AIRCAST=TRUE \
  psychlist/docker-airconnect-arm
ape404 commented 2 years ago

Many thanks for your help.

I can now start the container and the response is a long number (which I think is the identification for the container) see below:

@.***:~ $ docker run -d \

--net=host \

--name=airconnect \

--restart=unless-stopped \

-e SUPPRESS_FLUSH=TRUE \

-e INCLUDE_AIRCAST=TRUE \

psychlist/docker-airconnect-arm

3021f797de008efc3c4607162f0ceb07fff3abb819024e56737c9236f85e15c0

However, I can’t see the SONOS speakers on my iPhone as airplay items. Are there any additional settings necessary?

Albert Peter-Jordi

Passwangstrasse 15

4411 Seltisberg

Tel. +41 61 911 0744

eMail @.> @.

Von: pwt @.> Gesendet: Mittwoch, 19. Oktober 2022 17:21 An: pwt/docker-airconnect-arm @.> Cc: ape404 @.>; Author @.> Betreff: Re: [pwt/docker-airconnect-arm] Permission denied / no such container : airconnect (Issue #12)

Hi:

Looks like your docker installation isn't set up correctly, because you're getting a generic Docker permission error. Please try:

sudo docker run --rm hello-world

If that succeeds, then your user pi is probably not a member of the docker group. Have you done the following as in the Docker installation instructions?

sudo usermod -aG docker pi

If not, please do so, then start a new shell for it to take effect, and try the airconnect container again.

Finally, as a last resort, start the container as root:

sudo docker run --rm -d \ --net=host \ --name=airconnect \ --restart=unless-stopped \ -e SUPPRESS_FLUSH=TRUE \ -e INCLUDE_AIRCAST=TRUE \ psychlist/docker-airconnect-arm

— Reply to this email directly, view it on GitHub https://github.com/pwt/docker-airconnect-arm/issues/12#issuecomment-1284185558 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7YXBAKPS7FSFHW2ZGZH6DWEAGWVANCNFSM6AAAAAARJGHR6Y . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AF7YXBCXO4W7J7QOY6JVY5DWEAGWVA5CNFSM6AAAAAARJGHR62WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSMRMO5M.gif Message ID: @. @.> >

This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/

pwt commented 2 years ago

No further settings should be required. Could you please supply the output of:

docker logs airconnect

That will tell us which speakers (if any) have been discovered.

ape404 commented 2 years ago

This is the content of the log file:

@.***:~ $ docker logs airconnect

[17:55:29.457241] main:974 Starting aircast version: v0.2.51.2 (Nov 1 2021 @ 23:30:44)

[17:55:29.483257] main:1420 Starting airupnp version: v0.2.51.2 (Nov 1 2021 @ 23:32:10)

[17:55:29.535513] Start:1130 Binding to 192.168.0.101:49152

[22:17:32.986885] main:974 Starting aircast version: v0.2.51.2 (Nov 1 2021 @ 23:30:44)

[22:17:33.166670] main:1420 Starting airupnp version: v0.2.51.2 (Nov 1 2021 @ 23:32:10)

[22:17:33.241172] Start:1130 Binding to 172.17.0.1:49152

[22:18:33.242931] MainThread:924 IP change detected 172.17.0.1

[22:18:33.243151] Stop:1193 terminate update thread ...

[22:18:33.244082] Stop:1198 flush renderers ...

[22:18:33.244202] Stop:1201 terminate libupnp

[22:18:33.800823] Start:1130 Binding to 169.254.86.170:49152

[22:19:04.002778] MainThread:924 IP change detected 169.254.86.170

[22:19:04.002927] Stop:1193 terminate update thread ...

[22:19:04.003425] Stop:1198 flush renderers ...

[22:19:04.003538] Stop:1201 terminate libupnp

[22:19:04.559388] Start:1130 Binding to 192.168.0.101:49152

@.***:~ $

and this are the SONOS speakers that are bound in the same network:

It seems that none of them have been detected, the IP 192.168.0.101 that is mentioned in the log is the LAN address of the raspi.

Regards

Albert

Von: pwt @.> Gesendet: Mittwoch, 19. Oktober 2022 23:19 An: pwt/docker-airconnect-arm @.> Cc: ape404 @.>; Author @.> Betreff: Re: [pwt/docker-airconnect-arm] Permission denied / no such container : airconnect (Issue #12)

No further settings should be required. Could you please supply the output of:

docker logs airconnect

That will tell us which speakers (if any) have been discovered.

— Reply to this email directly, view it on GitHub https://github.com/pwt/docker-airconnect-arm/issues/12#issuecomment-1284585244 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7YXBAJXK5HUAIJXW3JSLTWEBQTRANCNFSM6AAAAAARJGHR6Y . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AF7YXBGL65OT5W7N4QMYYB3WEBQTRA5CNFSM6AAAAAARJGHR62WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSMSE3RY.gif Message ID: @. @.> >

This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/

ape404 commented 2 years ago

I have been able to solve the problem.

My rpi has been set to 192.168.0.101 which has been set as outside of the dhcp range which has been set up to 100.

After rearranging the rpi to a lower address the connection started to work properly.

Thanks for your great help and best regards

Albert

Von: pwt @.> Gesendet: Mittwoch, 19. Oktober 2022 23:19 An: pwt/docker-airconnect-arm @.> Cc: ape404 @.>; Author @.> Betreff: Re: [pwt/docker-airconnect-arm] Permission denied / no such container : airconnect (Issue #12)

No further settings should be required. Could you please supply the output of:

docker logs airconnect

That will tell us which speakers (if any) have been discovered.

— Reply to this email directly, view it on GitHub https://github.com/pwt/docker-airconnect-arm/issues/12#issuecomment-1284585244 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7YXBAJXK5HUAIJXW3JSLTWEBQTRANCNFSM6AAAAAARJGHR6Y . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AF7YXBGL65OT5W7N4QMYYB3WEBQTRA5CNFSM6AAAAAARJGHR62WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSMSE3RY.gif Message ID: @. @.> >

This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/

pwt commented 2 years ago

Great! I'm glad you got it to work.

The logs you supplied evidently showed that something related to IP addresses was misconfigured. I wouldn't expect to see repeated instances of lines like:

[22:18:33.242931] MainThread:924 IP change detected 172.17.0.1

So the Pi was flapping between its LAN IP address 192.168.0.101 and other local/link-local addresses.