Closed hongbo-miao closed 2 years ago
Seems the database got polluted by my previous experiment, manually dropped all tables and created again solves the issue!
@Hongbo-Miao
For some reason the default behavior for docker compose
is to reuse existing containers, even when not using volumes.
This is not very intuitive, because the db is not recreated every time you run compose - and indeed the db can be polluted.
The best way to circumnavigate this, is to run docker compose
with --force-recreate
.
this command will recreate all containers (from the docker image) and give you clean state on load:
docker compose up --force-recreate
@Hongbo-Miao
also, you can see in the output which containers are recreated and which ones are reused:
[+] Running 4/4
⠿ Container opal-fetcher-postgres_broadcast_channel_1 Created 0.0s
⠿ Container opal-fetcher-postgres_example_db_1 Created 0.0s
⠿ Container opal-fetcher-postgres_opal_server_1 Created 0.0s
⠿ Container opal-fetcher-postgres_opal_client_1 Recreated
I was using docker compose --build -V
, and not work.
It is --force-recreate
. Thanks for sharing!
Hi OPAL team, hmm, I started to get this error today for this repo. Any idea? Thanks!