taylorbourne / xteve_lazystream

Docker bundle that provides xTeVe and guide2go for enhanced guide data and Plex/Emby IPTV integration, and Lazystream for integrated high-quality NHL and MLB games.
71 stars 26 forks source link

aarch64 startup issue #90

Open nkm8 opened 1 year ago

nkm8 commented 1 year ago

I updated the aarch64 dockerfile with the latest changes, but I am still having an issue getting the image to run:

[update-lazystream] checking for update
[update-lazystream] installed version: v1.12.1
[update-lazystream] remote version: v1.12.1
[update-lazystream] latest version already installed
[cont-init.d] 60-update-lazystream: exited 0.
[cont-init.d] 70-chown-files: executing... 
[cont-init.d] 70-chown-files: exited 0.
[cont-init.d] 99-firstrun: executing... 
Are you sure you want to trust it? (y/N): exec: fatal: unable to exec bash
: No such file or directory
[cont-init.d] 99-firstrun: exited 127.
[cont-init.d] done.
[services.d] starting services
exec: fatal: unable to exec bash
: No such file or directory
exec: fatal: unable to exec bash
: No such file or directory
[services.d] done.
exec: fatal: unable to exec bash
: No such file or directory
exec: fatal: unable to exec bash
: No such file or directory
exec: fatal: unable to exec bash
: No such file or directory

I'm not quite sure what is happening, but it appears to be specific to s6-overlay because I am able to successfully run cronjob.sh directly from within the container. However, I am not able to access xteve via browser.

taylorbourne commented 1 year ago

hopefully your PR fixes all of the above!

nkm8 commented 1 year ago

@taylorbourne Unfortunately, I saw these issues with the changes in my PR already applied. Without my changes, the aarch64 image wouldn't run at all.