Docker issue on Debian 10 about intrigue-core HOT 11 CLOSED

Hi, I just did a fresh docker pull and launch ok in ubuntu 18.04 lts, so little different environment. I'm wondering if it's something with docker. Did you remove the versions that came built in to the distro and install the latest from docker?
https://docs.docker.com/engine/install/debian/

from intrigue-core.

from intrigue-core.

Any update on this?

from intrigue-core.

Sorry, I still didn't resolve this.
I checked my Docker version, but at the time I already installed it following the link by @JoeUser47.
I tried without -v option too but I'm still receiving the same error.
I just saw that another user opened an issue that looks very similar to mine (#129).
I don't know what else try, since my Docker knowledge is very basic at the moment.

from intrigue-core.

No problem, we'll do a little testing to ensure the data directory remapping is working as intended. Appreciate the response.

from intrigue-core.

I'm also getting the exact same errors as OP but I'm running Ubuntu 18.04. At first I thought it was due to my reverse proxy but If I run it as shown in the guide I get the same issue, regardless of if I use -v or not.

I made the /home/myuser/intrigue-core-data:/data with the root user so the docker process should have read/write permissions I believe.

sudo mkdir intrigue-core-data

sudo docker compose up

docker-compose.yml:

...
  intrigueio:
    image: "intrigueio/intrigue-core:latest"
    restart: always
    ports:
      - "7777"
    environment:
      - LANG=C.UTF-8
    labels:
      - traefik.enable=true
      - traefik.backend=subdomain
      - traefik.frontend.rule=Host:subdomain.mydomain.com
      - traefik.docker.network=web
      - traefik.default.protocol=http
      - traefik.port=80
    networks:
      - web
    depends_on:
      - proxy
    volumes:
      -  /home/myuser/intrigue-core-data:/data```

from intrigue-core.

I installed Debian 10.3 & got the same as @glaterza6 . With docker running, went to container bash, su postgres, and set cluster directory with:
/usr/lib/postgresql/12/bin/initdb -D /data/postgres
then stopped and relaunched container, but got an error postgres 10 couldn't start because it was initialized with 12.
Went back to container bash, su postgres, rm files under /data/postgres, then set with 10.
/usr/lib/postgresql/10/bin/initdb -D /data/postgres
Stopped and relaunched container & it ran, starting 10, then 12. Not sure both are meant to be there. Hope it helps.

from intrigue-core.

Looks like we were accidentally installing both, due to this line in Dockerfile-standalone (

from intrigue-core.

Fix is up on master (removes installation of postgres 10, while staying on the base image of Ubuntu 18.04), and standalone image is currently rebuilding, eta 30min. Verified by building locally and the service is up and running as expected on startup.

from intrigue-core.

Can confirm it's now working on Ubuntu 18.04. Don't forget to delete the contents of the data folder if you used it before, it wasn't working for me until I deleted it and let it rebuild it.

Thanks for the quick fix!

from intrigue-core.

I confirm too that it works now!! Thank you very much for the fast support! :)

from intrigue-core.