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 compose ports are overridden once container is deployed #54

Closed
1 task done
tim-durrant opened this issue Mar 15, 2024 · 4 comments
Closed
1 task done

Docker compose ports are overridden once container is deployed #54

tim-durrant opened this issue Mar 15, 2024 · 4 comments

Comments

@tim-durrant
Copy link

tim-durrant commented Mar 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The Prowlarr Web UI should listen on the port specified in the docker compose file.

Expected Behavior

The Prowlarr Web UI configuration file overrides the port specified in the docker compose file.

Steps To Reproduce

I want Prowlarr to listen on port 9697. So in my docker compose, I have this:

ports: - 9697:9697

However once the docker container is deployed, it defaults to port 9696 in config.xml:

<Port>9696</Port>

I edited config.xml to be 9697 and Prowlarr was then accessible via the Web UI.

Environment

- OS:Ubuntu

CPU architecture

x86-64

Docker creation

prowlarr:
    image: lscr.io/linuxserver/prowlarr:latest
    container_name: prowlarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Australia/Brisbane
    volumes:
      - /nas/config/prowlarr/config:/config
    networks:
      default:
        ipv4_address: 172.20.0.36
    ports:
      - 9697:9697
    restart: always

Container logs

[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Prowlarr - /app/prowlarr/bin/Prowlarr - Version 1.12.2.4211 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Debug] Bootstrap: Console selected 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] MigrationController: *** Migrating data source=/config/prowlarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Debug] MigrationController: Took: 00:00:00.4218167 
[Info] MigrationController: *** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:9697 
[Info] CommandExecutor: Starting 3 threads for tasks. 
[ls.io-init] done.
[Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. 
[Info] Microsoft.Hosting.Lifetime: Hosting environment: Production 
[Info] Microsoft.Hosting.Lifetime: Content root path: /app/prowlarr/bin
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@aptalca
Copy link
Member

aptalca commented Mar 15, 2024

Map 9697:9696, don't edit the config

@aptalca aptalca closed this as completed Mar 15, 2024
@tim-durrant
Copy link
Author

This is fine with just one instance of Prowlarr. How would I edit the docker compose file for one Prowlarr listening on 9696 and a second Prowlarr listening on 9697?

@aptalca
Copy link
Member

aptalca commented Mar 15, 2024

9696:9696 on one and 9697:9696 on the other

https://github.com/linuxserver/docker-prowlarr?tab=readme-ov-file#parameters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants