Skip to content
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

premiumizearr won't start (since version 1.2.4) #62

Open
dabonzo opened this issue Aug 14, 2022 · 18 comments
Open

premiumizearr won't start (since version 1.2.4) #62

dabonzo opened this issue Aug 14, 2022 · 18 comments
Labels
bug Something isn't working docker

Comments

@dabonzo
Copy link

dabonzo commented Aug 14, 2022

Since the version 1.2.4, the app won't start anymore. v1.2.1 - v1.2.3 work fine.
The error from the log is

premiumizearr   | exec /init: exec format error
premiumizearr exited with code 1
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr exited with code 1
premiumizearr exited with code 1
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
premiumizearr   | exec /init: exec format error
@dabonzo
Copy link
Author

dabonzo commented Aug 14, 2022

Forgot to mention, it's docker

@JackDallas
Copy link
Owner

Had a few iffy releases, 1.2.6 seems stable for me, could you confirm this issue is still happening on 1.2.6, if it is I'll whip up a docker setup and have a look at it 👍

@JackDallas JackDallas added bug Something isn't working docker labels Aug 15, 2022
@dabonzo
Copy link
Author

dabonzo commented Aug 15, 2022

1.2.4, 1.2.5 and 1.2.6. Every release has that exec /init error.

@JackDallas
Copy link
Owner

Hey @dabonzo im gonna take a look at this but in currently banned from premiumize.me (one of my test runs spammed them a bit) and trying to resolve it so may be a bit delayed

@dabonzo
Copy link
Author

dabonzo commented Aug 17, 2022

@JackDallas let me know if you need help with that (premiumize.me)

@JackDallas
Copy link
Owner

@JackDallas let me know if you need help with that (premiumize.me)

@dabonzo haven't had a reply from them yet, going to send another message but will try and get the docker working while I wait for a reply

@JackDallas
Copy link
Owner

Hey @dabonzo so you know, no word from premiumize.me which does put this project in a bit of a sticky position, can you confirm for me though if you run using the v1.2.3 tag if it still runs ? if it does I'll see if a change I made caused this or if it's something weird upstream I didn't know I was depending on

@dabonzo
Copy link
Author

dabonzo commented Aug 19, 2022

@JackDallas , yes ghcr.io/jackdallas/premiumizearr:v1.2.3 still working.

@dabonzo
Copy link
Author

dabonzo commented Aug 19, 2022

Didn't pull a new 1.2.3 version though, using the old cached local one that worked all the time anyway.

@dabonzo
Copy link
Author

dabonzo commented Aug 21, 2022

@JackDallas was playing around a little bit and I think the base image doesn't work. I've used the latest alpine FROM ghcr.io/linuxserver/baseimage-alpine:3.16-cbed9854-ls16 in Dockerfile.amd64 in the docker directory. Seems it works for me. I also tested docker image on a raspberry pi. On the raspi (arm) the latest version worked all the time. So it's very probable the baseimage that creates the issue.

@JackDallas
Copy link
Owner

Thanks for looking in to that @dabonzo really appreciate it. I knew I shouldn't have used that base image 🤦 I'm gonna see if I can get it working permissions and all in a boring old alpine container. Fingers crossed it's not to hellish

@dabonzo
Copy link
Author

dabonzo commented Aug 22, 2022

I would help more but, with a PR, but I can't test it, upload the docker image. I've managed to get the build process going but that's it. I'm no developer so anything more than commit, push, pull is something new I need to learn to me :D

@JackDallas
Copy link
Owner

ngl I have it setup a weird way, I need to write a contributors guide to make it more straight forward tbh. atm to build it you have to do it by installing goreleaser and running goreleaser --rm-dist --snapshot a lot of the logic is tied in to that.

I've made an image, it can read and write the config, premiumize's servers are down atm, I'll check again later but in the mean time I've pre-released the changes on the dev tag on docker

https://github.com/jackdallas/Premiumizearr/pkgs/container/premiumizearr/39003370?tag=dev

@ensingerphilipp
Copy link

Bump would love to see this work again

@vmpr
Copy link

vmpr commented Jul 9, 2024

I got the same problem :( is there any solution?

@cat24max
Copy link

I got the same problem :( is there any solution?

This is because of the CPU arch. Try "v1.2.7-rc1-amd64". It leems like the current latest is maybe only ARM?

@besendorf
Copy link

besendorf commented Jan 21, 2025

I am still experiencing this bug. Changing the base image seems like not so much of a problem. What's the status on this?@JackDallas ?

I just saw that there is already a PR and it even was approved by someone else. #63

@ensingerphilipp
Copy link

ensingerphilipp commented Jan 21, 2025

@besendorf

  1. Use 1.27rc1 in Docker Container:
    https://github.com/jackdallas/Premiumizearr/pkgs/container/premiumizearr

  2. Make sure all Datafolders are owned by GID UID 1000

  3. Try using this Docker command:

docker run -d \
    --name premiumizearr \
    -v /home/USER/storage/downloads/premiumize/data:/data \
    -v /home/USER/storage/downloads/premiumize/blackhole:/blackhole \
    -v /home/USER/storage/downloads/premiumize/downloads:/downloads \
    -v /home/USER/storage/downloads/premiumize/unzip:/unzip \
    -e PGID=1000 \
    -e PUID=1000 \
    -p 8182:8182 \
    --restart unless-stopped \
    ghcr.io/jackdallas/premiumizearr:dev

Of Course change the Folder Structure to yours haha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working docker
Projects
None yet
Development

No branches or pull requests

6 participants