-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails with apt-get not found #34
Comments
I will probably need to make a separate build container for alpine, I did already update the nightly tag for alpine but the dockerfile can't handle the conditionals I'll see if I can come up with something |
Thank you. Looks like they are rebasing a few containers to Alpine: https://info.linuxserver.io/affected/notifications/ Not sure if this will eventually apply to other tags as well, or if it's just being done for space efficiency with the nightly builds. |
Just pushed an update, I already had accounted for most of this in the 90-sma-config file when I made the sma-mod so since the build dockerfile can be alpine or ubuntu I just removed most of the packages from that and will let 90-sma-config do the work Only thing I wasn't sure of is if alpine has an equivalent package to Let me know if that works |
Thanks again. Build works now. Will have to wait for the next grab to see how the tag/conversion goes. |
Double check your docker logs when starting the container for the first time for any errors (from 90-sma-config) since I moved most of the container setup to occur on the first launch and they might be hiding in there and not immediately apparent |
Here's what I found...
I think I've always had the chown errors but it's worked fine. Not sure about the other errors |
Looks like it isn't doing the initial git pull, script won't work Made a tweak, try the latest update (the permissions error looks like you have a .bak file that it cannot access, you could probably fix the ownership on that .bak or move it out of your mounted directory to make that go away) |
Now getting this:
|
Alright I spun up a test container and think I have everything sorted now, try one more time The |
Looking pretty good now...
|
Sweet, alright the build container should be universal now alpine or ubuntu, thanks for the tests Closing this out reopen if you have any issues |
[don't have rights to reopen] The conversion is failing. Here is the log file...
ffprobe is there but gives an error when you try to execute it:
If I switch the ffmpeg tag to
|
Yeah looks like the FFMPEG build from the ubuntu containers does not work on alpine and the jrottenberg container only goes up to alpine 313 (linuxserver radarr container on 315) The ffmpeg APK included in alpine however appears to contain VAAPI so I added some new options and this appears to be working for me. You'll need to include your hw devices and volumes etc but that's the environment variables needed radarr:
image: ghcr.io/mdhiggins/radarr-sma:nightly
container_name: radarr
environment:
- PUID=${PUID}
- PGIG=${PGID}
- TZ=${TZ}
- SMA_USE_REPO=true
- SMA_HWACCEL=true Update: SMA_USE_REPO defaults to true on nightly, can leave that out on latest build |
Thank you. Rebuilt container and will test with a file later. |
So the conversion and tagging worked, but the rename failed:
However, the file is named correctly. Side note, I have |
Hm it almost looks like the API just failed to return anything. Is it doing this for every file or was this a one off error? If it's doing it for every file could you turn on debug logging and send a full log from postRadarr |
Looks like every file. Here's a debug log: https://pastebin.com/bx3xhZwk |
Fixed in latest version of SMA |
Docker compose file contains:
Get the following error on
docker-compose build
LinuxServer.io rebased the nightly tag to Alpine: https://info.linuxserver.io/issues/2022-02-03-radarr/
Can this be accounted for in your dockerfile?
The text was updated successfully, but these errors were encountered: