Trouble starting docker image

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
ritmo2k
Newbie
Newbie
Posts: 4
Joined: November 9th, 2014, 4:02 pm

Trouble starting docker image

Post by ritmo2k »

I am trying to run 4.2.1 from the linuxserver/sabnzbd container using podman in Alma Linux.

When I start the container I get the following error:

Fatal error:
Unable to bind to port 8080 on localhost. Some other software uses the port or SABnzbd is already running.

I don't have anything running on port 8080, I am certain as I have verified with lsof and netstat. Selinux is also disabled.

Any ideas about what may be the problem?
User avatar
sander
Release Testers
Release Testers
Posts: 8832
Joined: January 22nd, 2008, 2:22 pm

Re: Trouble starting docker image

Post by sander »

choose a different outside port in your sabnzbd docker config
ritmo2k
Newbie
Newbie
Posts: 4
Joined: November 9th, 2014, 4:02 pm

Re: Trouble starting docker image

Post by ritmo2k »

Actually, further research into this reveals I have the same issue as github linuxserver/docker-sabnzbd #82

ipv6 is disabled on my host (and that won't change).

It looks like there is a facility to alter the containers runtime behavior that I am looking into now.
ritmo2k
Newbie
Newbie
Posts: 4
Joined: November 9th, 2014, 4:02 pm

Re: Trouble starting docker image

Post by ritmo2k »

I am able to modify the container startup to pass 127.0.0.1:8080 to the --server parameter (I cannot use 0.0.0.0 with any port).

I have started the container and published the port, yet using curl from the container host, there is no response?

Does anyone have any suggestions?
Post Reply