Is there a docker image repo for the new version?

[famewolf]

I'm currently running nzbget on my Truenas. I didn't see anything mentioned about docker?

[ghost]

Would like this as well. Wish https://github.com/linuxserver/docker-nzbget this project would just use this repo.

Any way @hugbug could transfer ownership of the original repo to nzbget-ng?

[NineBall8]

https://hub.docker.com/r/jscottelblein/nzbget This should work I think.

[pannal]

Hmm, I'm using this docker image now. NZBget shows nzbget 21.2-testing-r2333 server-mode - is that correct?

[Mouton99]

I am using my own docker image (built using this fork or github.com/linuxserver/docker-nzbget), and I see Currently installed: 21.3-rc1-12-ga70a383c

jscottelblein/nzbget was not updated for 6 months, so it contains a version from 6 months ago.

[pannal]

My hero, thank you! nzbget 21.3-rc1-12-ga70a383c server-mode

[famewolf]

I'll add my thanks as well!

[fabiorzfreitas]

I am using my own docker image (built using this fork or github.com/linuxserver/docker-nzbget), and I see Currently installed: 21.3-rc1-12-ga70a383c

@Mouton99 ,

Hi, thank you for providing this image! But it has a serious issue: it doesn't seem to be able to detect architectures correctly. I tried using the same syntax from linuxserver, mouton99/nzbget-ng:arm64v8-latest (which I tested against their image and it worked properly), but it's not available on your image.

I'm running everything from a Raspeberry Pi 4B 8GB, using both Portainer and Docker CLI to make sure this is correct.

I checked both repos for occurences of "arm64v8" and there were only two matches (besides the readme): Dockerfile.aarch64, which was a perfect match between the 2 repos, and the Jenkinsfile, which had a few different lines.

I would have submitted a PR, but since I still have very little knowledge on Docker, I figured it would be better to come back here, where I found your image!

[Mouton99]

Hi, thank you for providing this image! But it has a serious issue: it doesn't seem to be able to detect architectures correctly. I tried using the same syntax from linuxserver, mouton99/nzbget-ng:arm64v8-latest (which I tested against their image and it worked properly), but it's not available on your image.

I am indeed only building and publishing for linux/arm64, not any other arch.

What you can do is simply git clone my fork, then run docker build -t nzbget-ng . from within that folder. That will give you a local image that you can use with docker run ... nzbget-ng

[famewolf]

Hi, thank you for providing this image! But it has a serious issue: it doesn't seem to be able to detect architectures correctly. I tried using the same syntax from linuxserver, mouton99/nzbget-ng:arm64v8-latest (which I tested against their image and it worked properly), but it's not available on your image.

I am indeed only building and publishing for linux/arm64, not any other arch.

What you can do is simply git clone my fork, then run docker build -t nzbget-ng . from within that folder. That will give you a local image that you can use with docker run ... nzbget-ng

I wish you'd mentioned that before...I'm guessing then mine is not pulling even though pointed to your build and I can't do a docker build on a truenas scale install which uses kubernetes for managing containers. Guess I'll point it back to the original. Mine says it's nzbget 21.4-rc2 server-mode So wonder who's I'm running at this point.

[fabiorzfreitas]

Hi, thank you for providing this image! But it has a serious issue: it doesn't seem to be able to detect architectures correctly. I tried using the same syntax from linuxserver, mouton99/nzbget-ng:arm64v8-latest (which I tested against their image and it worked properly), but it's not available on your image.

I am indeed only building and publishing for linux/arm64, not any other arch.

What you can do is simply git clone my fork, then run docker build -t nzbget-ng . from within that folder. That will give you a local image that you can use with docker run ... nzbget-ng

@Mouton99

I surely can do that, but it so happens that I'm also trying build for linux/arm64v8, but it seems that your image assigns me amd, which, of course, doesn't work for me. I checked that with Docker inspect, for the package's architecture I was receiving.

I can't say for sure that this is on the Jenkinsfile, but if it is, I'd be more than happy to submit a PR specifying docker to always fetch either linux/nzbget-ng:arm64v8-latest or linux/nzbget-ng:arm64v8-testing, whichever you're maontaining!

[x86txt]

If anyone wants a linux/amd64 build of @Mouton99's repo, you can find it here: https://hub.docker.com/repository/docker/x86txt/nzbget-ng

I'll update it as mouton909's pushes new updates to his repo.

[fabiorzfreitas]

@x86txt thank you for this. I really intended to do it, as I said, but I think I'd only be able to work on it anout 2 or 3 months for now, maybe more

[pannal]

If anyone wants a linux/amd64 build of @Mouton99's repo, you can find it here: https://hub.docker.com/repository/docker/x86txt/nzbget-ng

I'll update it as mouton909's pushes new updates to his repo.

I think you meant arm64, right? As @Mouton99's image already is amd64

[x86txt]

Yep, I built it for both actually. The GitHub Action is the same either way.

[luckedea]

Please refer to #106 (comment)
I understand this is not fully the same question, but after the nzbget-ng and nzbgetcom migration we would be supporting the docker version ourselves. At the moment not all improvements from nzbget-ng exist here, but some are, some other problems were resolved too (differently).

I'm going to close this issue and keep #84 (comment) as main issue on the Docker subject.