Trouble setting up on docker on raspi. Can't bind to 0.0.0.0

[santosh]

Hello, here is the docker compose I used to create postgres instance on my machine:

version: '3.9'

services:
  postgres:
    image: postgres:latest
    container_name: pg-on-raspi
    restart: always
    environment:
      POSTGRES_DB: santosh
      POSTGRES_USER: santosh
      POSTGRES_PASSWORD: mypass
    ports:
      - "5432:5432"
    volumes:
      - postgres_data:/var/lib/postgresql/data

  pgadmin:
    container_name: pgadmin
    image: dpage/pgadmin4
    depends_on:
      - postgres
    ports:
      - "5050:80"
    environment:
      PGADMIN_DEFAULT_EMAIL: my@e.mail
      PGADMIN_DEFAULT_PASSWORD: mypass
    restart: unless-stopped

volumes:
  postgres_data:

Before running the Planka, I have already created a planka database on this postgres instance. I am using this docker-compose.yml file to spin up Planka.

version: '3'

services:
  planka:
    image: ghcr.io/plankanban/planka:latest
    restart: on-failure
    volumes:
      - user-avatars:/app/public/user-avatars
      - project-background-images:/app/public/project-background-images
      - attachments:/app/private/attachments
    ports:
      - 3333:1337
    environment:
      - BASE_URL=http://localhost:3333
      - DATABASE_URL=postgresql://santosh:santosh@192.168.0.100/planka
      - SECRET_KEY=3473d70182c58bfc9b836720080dd9de6790077f051a43854079e930e0affe3f1942d00e862d6b4b710cd071430b0722eef19c5169796375e558c3f7759bbe5a

      - DEFAULT_ADMIN_EMAIL=my@e.mail
      - DEFAULT_ADMIN_PASSWORD=mypass
      - DEFAULT_ADMIN_NAME=Santosh Kumar
      - DEFAULT_ADMIN_USERNAME=santosh

volumes:
  user-avatars:
  project-background-images:
  attachments:

Things to note here:

1. I have modified the DATABASE_URL to have the correct hostname of the database provider. As I exported the port from postgres container, it is directly available on host.
2. In the BASE_URL, I tried passing 0.0.0.0 so that it is available on all machine on the LAN, but docker stucks at Attaching to planka-1.
3. I don't plan to port forward to access the server. What fix can I make?
4. Docker at the moment shows this warning, which concerns me:

planka-1  | debug: It looks like your `sails.config.sockets.onlyAllowOrigins` array only includes
planka-1  | debug: references to the `localhost` origin.  This is completely valid, but be sure
planka-1  | debug: to add any other origins to this list that you'd like to accept socket
planka-1  | debug: connections from!
planka-1  | debug: 

If configuring this is necessary, how do I add hosts to allowOrigins on a running sever? Can I add a CIDR?

How can I make it more persistent? Because from where I can think. I need to get into the production container, kill the process, make config change (which file needs to be modified?), restart the server. What happens if raspi is restarted? Will it retain the settings?

[meltyshev]

Hi! I unfortunately can't answers to all the questions, as I'm not very familiar with the subject of servers and so on, but I can answer regarding BASE_URL. In the BASE_URL there should be an address that you are trying to access Planka in a browser, if you are trying to access it by IP, then it should be http://IP.

[santosh]

The logs seem to be stuck at Attaching to planka-1; don't know if that is suppose to be like that.

Anyway setting up BASE_URL as you suggested worked well. And I don't see the sails warning.

So I'll mark this as answer.