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

Docker Support: Change Image from linuxserver.io to nzbgetcom #84

Closed
VenimK opened this issue Jan 4, 2024 · 12 comments · Fixed by #140
Closed

Docker Support: Change Image from linuxserver.io to nzbgetcom #84

VenimK opened this issue Jan 4, 2024 · 12 comments · Fixed by #140
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@VenimK
Copy link

VenimK commented Jan 4, 2024

Now I'm using ghcr.io/linuxserver/nzbget:latest nzbget image...

Can I just change the link t this one ???

@toddrob99
Copy link

That's all I did (change ghcr.io/linuxserver/nzbget:latest to nzbgetcom/nzbget:latest in my docker-compose.yml file), aside from making a backup of my config folder first. So far it seems to be working fine.

@VenimK
Copy link
Author

VenimK commented Jan 6, 2024

That's all I did (change ghcr.io/linuxserver/nzbget:latest to nzbgetcom/nzbget:latest in my docker-compose.yml file), aside from making a backup of my config folder first. So far it seems to be working fine.

Getting error 400 on that :)

@Mouton99
Copy link

Mouton99 commented Jan 6, 2024

Worked for me too, after I removed the ArticleReadChunkSize line from my nzbget.conf
Was told by the Docker logs that this was not supported, so it was easy to identify and fix.
(I would guess this config came from a PR merged into nzbget-ng - which I used before this - that was not yet merged here.)

@luckedea luckedea changed the title Change Image Docker Support: Change Image from linuxserver.io to nzbgetcom Jan 8, 2024
@luckedea luckedea added bug Something isn't working enhancement New feature or request question Further information is requested labels Jan 8, 2024
@macmpi
Copy link

macmpi commented Jan 9, 2024

docker run with nzbgetcom/nzbget:latest gives

docker: Error response from daemon: missing signature key.

any hint?

@Mouton99
Copy link

Mouton99 commented Jan 9, 2024

docker run with nzbgetcom/nzbget:latest gives

docker: Error response from daemon: missing signature key.

any hint?

Did you try what Google seems to suggest for this error, namely upgrading the docker (daemon & cli) on your computer?

@macmpi
Copy link

macmpi commented Jan 10, 2024

It's running on a NAS which can't be much upgraded unfortunately...
However curious as to why I can't install that specific container while many others run just fine, including previous linuxserver instances.

@phnzb
Copy link
Collaborator

phnzb commented Jan 10, 2024

migration from linuxserver/nzbget or docker-nzbget-ng

nzbgetcom/nzbget docker image is using the same layout as linuxserver image, so miration is simple:

  1. Direct migration - change image in docker-compose.yml to nzbgetcom/nzbget:TAG or ghcr.io/nzbgetcom/nzbget:TAG
    where TAG can be:
  • latest - for stable releases
  • testing - for development releases
  1. In case of migration from nzbget-ng docker image or from nzbgetcom/nzbget:testing to nzbgetcom/nzbget:latest - you have to delete ArticleReadChunkSize string from the config file. This setting is supported only on :testing images now (v22 testing, or upcoming v23 latest)

  2. To correct unpacking issues Check Settings - Unpack commands:

  • UnrarCmd must be unrar
  • SevenZipCmd must be 7z
  1. Extensions - please note, nzbgetcom/nzbget is bundled with Python 3.11, so check that your extensions work with this Python version.
    nzbgetcom provides fixes for popular extensions, update yours if needed:
    FailureLink
    VideoSort
    FakeDetector

  2. For specific cases please try:

  • backup all nzbget settings (NZBGet UI: Settings - System - Backup Settings)
  • down old container, remove nzbget.conf, replace image, start with clean config and restore setting (NZBGet UI: Settings - System - Restore Settings)
  1. If nzbgetcom/nzbget image does not work, please post more information here, but please provide
  • system on which you tried to run nzbget in docker (at least - architecture, for NAS - model, etc)
  • docker version
  • docker logs

So we can troubleshoot and assist.

@macmpi
Copy link

macmpi commented Jan 11, 2024

On TerraMaster F2-210 NAS:

~$ sudo docker info     
Containers: 2
 Running: 1
 Paused: 0
 Stopped: 1
Images: 2
Server Version: 17.06.0-dev
Storage Driver: btrfs
 Build Version: Btrfs v4.7.3
 Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3addd840653146c90a254301d6c3a663c7fd6429
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Kernel Version: 4.4.18-g8bcbd8a-dirty
Operating System: <unknown>
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 960.6MiB
Name: My-nas
ID: EITG:YOYC:3FM7:32PZ:JSTB:M6DU:27B3:ZXJL:6XVR:G2LH:MQ4E:AM3W
Docker Root Dir: /mnt/md0/appdata/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 https://registry.hub.docker.com/
Live Restore Enabled: false

WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

~$ sudo docker version 
Client:
 Version:      unknown-version
 API version:  1.30
 Go version:   go1.7.4
 Git commit:   unknown-commit
 Built:        unknown-buildtime
 OS/Arch:      linux/arm64

Server:
 Version:      17.06.0-dev
 API version:  1.31 (minimum version 1.12)
 Go version:   go1.7.4
 Git commit:   6d92b0ee1
 Built:        Sun May 22 01:10:00 2016
 OS/Arch:      linux/arm64
 Experimental: false

log on installing container:

time="2024-01-11T16:38:37.372033000+01:00" level=warning msg="Could not get operating system name: Error opening /usr/lib/os-release: open /usr/lib/os-release: no such file or directory" 
time="2024-01-11T16:38:38.954313000+01:00" level=info msg="Attempting next endpoint for pull after error: missing signature key" 
time="2024-01-11T16:38:40.339434000+01:00" level=info msg="Attempting next endpoint for pull after error: missing signature key" 
time="2024-01-11T16:38:40.339619000+01:00" level=error msg="Handler for POST /v1.30/images/create returned error: missing signature key" 

@luckedea luckedea added documentation Improvements or additions to documentation and removed bug Something isn't working enhancement New feature or request labels Jan 12, 2024
@phnzb
Copy link
Collaborator

phnzb commented Jan 12, 2024

@macmpi
It looks like your problem is caused by a modern docker buildx that provides images with oci media types if oci annotations are provided. Old versions of docker do not work with these images.
Test if you can next image: nzbgetcom/nzbget:bugfix-docker-disable-oci-mediatypes. You can just pull, if it pulls successfully, then everything is ok:

docker pull nzbgetcom/nzbget:bugfix-docker-disable-oci-mediatypes

If your problem goes away, I will rebuild and push docker images with docker media types to provide compatibility with older Docker installations (like yours).

@macmpi
Copy link

macmpi commented Jan 12, 2024

Good catch, thanks!
Looking forward the update.

@phnzb
Copy link
Collaborator

phnzb commented Jan 17, 2024

@macmpi all nzbget images has been updated (latest, testing and v22).

@macmpi
Copy link

macmpi commented Jan 17, 2024

👍 thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants