Thanks for the tips, that’s put me on the track. However I’m still having some issues as I think the container names are overlapping.
What I have done:
- left my current discourse container running (I figure if I have this right than the other container should be able to continue running) - I don’t want to share any resources (separate postgres databases).
- cloned a discourse repo to a new folder (/opt/discourse_new)
- edited the
./containers/app.yml file, changed the following values (and added email settings)
- "20081:80" # fwd host port 20081 to container port 80 (http)
## The Docker container is stateless; all data is stored in /shared
Then I ran
./launcher bootstrap app
However it fails out when it tries to stop postgres
Pups::ExecError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return #<Process::Status: pid 20 exit 1>
Is there a way to tell discourse to create a new postgresql instance rather than reusing or disturbing the previous one?