On following run instructions (clone repo, copy sample environment and docker file) and running quickstart.py, I am unable to create a new user in the API.
The only changes made to env_prod.list is replacing the example domains with localhost
result of docker logs $containerID
<Long python tracelog leading to actual error>
django.db.utils.OperationalError: (1130, "Host '172.18.0.3' is not allowed to connect to this MariaDB server")
Where 172.18.0.3 is the default IP given to the API container by docker.
This error also occurs when running docker-compose -f docker-prod.yml run --rm --entrypoint 'python manage.py createsuperuser' api or running docker exec -it $containerID /bin/sh and attempting to manipulate the database in any way via django-admin/manage.py
This has only recently begun to occur, I've also tried this after wiping /var/lib/docker for the sake of argument, but don't know why this suddenly has started happening.
It is worth mentioning I have not yet been able to get this to work at all, previously it has been a slew of other problems that seem to appear and resolve almost at random, but this is one that is now reappearing no matter what changes I make to the configs or when cloning the repo clean.
On following run instructions (clone repo, copy sample environment and docker file) and running quickstart.py, I am unable to create a new user in the API.
The only changes made to env_prod.list is replacing the example domains with localhost
result of docker logs $containerID
Where
172.18.0.3
is the default IP given to the API container by docker.This error also occurs when running
docker-compose -f docker-prod.yml run --rm --entrypoint 'python manage.py createsuperuser' api
or runningdocker exec -it $containerID /bin/sh
and attempting to manipulate the database in any way via django-admin/manage.pyThis has only recently begun to occur, I've also tried this after wiping /var/lib/docker for the sake of argument, but don't know why this suddenly has started happening.
It is worth mentioning I have not yet been able to get this to work at all, previously it has been a slew of other problems that seem to appear and resolve almost at random, but this is one that is now reappearing no matter what changes I make to the configs or when cloning the repo clean.