Closed crozo5 closed 3 years ago
philippe44
commented
4 years ago I don't use docker much in the context of NAS in particular. So, we'll have to wait for somebody else to show up. If you are in host mode, it should be fine, all what is needed is to make sure that there is no NAT and no firewall
pwt
commented
4 years ago Is there a way of seeing the logs from the container(s)? The equivalent of docker logs <container_name>.
crozo5
commented
4 years ago Is there a way of seeing the logs from the container(s)? The equivalent of
docker logs <container_name>.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 911
User gid: 911
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-install: executing...
Checking for valid arch options
Proceeding with x86-64 arch
--2020-10-19 17:27:43-- https://raw.githubusercontent.com/philippe44/AirConnect/master/bin/airupnp-x86-64
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.132.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.132.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 685912 (670K) [application/octet-stream]
Saving to: ‘/bin/airupnp-x86-64’
/bin/airupnp-x86-64 100%[===================>] 669.84K 3.05MB/s in 0.2s
2020-10-19 17:27:44 (3.05 MB/s) - ‘/bin/airupnp-x86-64’ saved [685912/685912]
--2020-10-19 17:27:44-- https://raw.githubusercontent.com/philippe44/AirConnect/master/bin/aircast-x86-64
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.132.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.132.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 588120 (574K) [application/octet-stream]
Saving to: ‘/bin/aircast-x86-64’
/bin/aircast-x86-64 100%[===================>] 574.34K --.-KB/s in 0.1s
2020-10-19 17:27:44 (5.03 MB/s) - ‘/bin/aircast-x86-64’ saved [588120/588120]
[cont-init.d] 30-install: exited 1.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2020-10-19 17:27:45,283 CRIT Supervisor running as root (no user in config file)
2020-10-19 17:27:45,296 INFO supervisord started with pid 259
2020-10-19 17:27:46,299 INFO spawned: 'airupnp-x86-64' with pid 268
2020-10-19 17:27:46,304 INFO spawned: 'aircast-x86-64' with pid 269
2020-10-19 17:27:47,473 INFO success: airupnp-x86-64 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-19 17:27:47,473 INFO success: aircast-x86-64 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-19 17:27:47,473 INFO success: aircast-x86-64 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) I think you need to look at the logs from airupnp/aircast, not from the wrapper process. They should look something like:
17:12:48.408319] main:1385 Starting airupnp version: v0.2.27.0 (Aug 3 2020 @ 11:17:22)
[17:12:48.445605] Start:1103 Binding to 192.168.0.250:49152
[17:12:49.119304] AddMRDevice:991 [0x97558]: adding renderer (Move)
[17:12:49.119610] AddMRDevice:1012 [0x97558]: cannot get mac Move+, creating fake 5260476a
[17:12:49.146272] MasterHandler:655 [0x97558]: subscribe successI think you need to look at the logs from airupnp/aircast, not from the wrapper process. They should look something like:
17:12:48.408319] main:1385 Starting airupnp version: v0.2.27.0 (Aug 3 2020 @ 11:17:22) [17:12:48.445605] Start:1103 Binding to 192.168.0.250:49152 [17:12:49.119304] AddMRDevice:991 [0x97558]: adding renderer (Move) [17:12:49.119610] AddMRDevice:1012 [0x97558]: cannot get mac Move+, creating fake 5260476a [17:12:49.146272] MasterHandler:655 [0x97558]: subscribe success
Where can found this logs? I use Container Station from QNAP
pwt
commented
4 years ago Sorry -- I don't know anything about Container Station.
crozo5
commented
4 years ago Sorry -- I don't know anything about Container Station.
It's like Portainer but in QNAP
philippe44
commented
3 years ago AirConnect puts the logs where the it is told to (-f on the command line and stderr if none given, so in systemd vased system, you can retrieve them using systemd log), so unfortunately I don't know in the case of this container what config / command line is being used
jacoknapp
commented
3 years ago Best way to do this might be to just log in through SSH on QNAP and run it through the docker cli. Personally this is what i do for my 20 or so containers that I run. You will still see them inside container station, you just won't have to manage it that way.
That said if you want to turn on the --restart=always flag you actually have to do this with a qnap api call, or through the window. This allows you to just run a script to update the containers.
Also In order to work you are going to need to pass in the the broadcast ip. For example if you use the 1activegeek/airconnect:latest container image you will want to pass the environment variable AIRCAST_VAR or AIRUPNP_VAR and set that equal to "-b ip_addr" where ip_addr is the IP address of your nas.
philippe44
commented
3 years ago Closed for inactivity
I have a QNAP NAS with an Intel Celeron CPU, I am trying to install this docker through Container Station with network HOST, but I cannot find any Chromecast or Google Home device. I have seen that this docker is made for arm, arm64 and amd64. I don't know if there is the problem.
LOGS: