We run into the same issue. Adding DISCOURSE_MAXMIND_ACCOUNT_ID
to the env fixed this for me.
Strike that, I first assumed that the container build successfully, but that was not the case.
We run into the same issue. Adding DISCOURSE_MAXMIND_ACCOUNT_ID
to the env fixed this for me.
Strike that, I first assumed that the container build successfully, but that was not the case.