-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to seed database #30
Comments
I am also having this issue and it is preventing installation. Any ETA for a fix or a workaround? |
I can also say I've encountered this issue. If it helps at all, I didn't have any issues when installing on Ubuntu Server 18.04, but I do encounter it with RHEL 7.7. Additionally, I was only able to get to this error by modifying the DockerCompose file for the production django container (I haven't tried on local at all in RHEL). I had to change |
I've been able to get past this database seeding issue, but I'm not entirely sure whats changed. I ended up starting over from scratch, and making all my customization for the production environment before running any of the commands to get the application started. |
From the information provided here and elsewhere the issue appears to be related to Docker on certain Linux distros. It has come up a few times when using a basic Linux AMI on AWS and is resolved when users switch to Ubuntu. I have not encountered it on macOS, Debian, or Ubuntu myself thus far. You will likely encounter issues if you customize the database or input data before seeding the database. Attempts to overwrite custom data with the seed data may throw errors and prevent you from proceeding. |
I was on macOS when I encountered the issue, and I did not customize the database or input data before seeding. |
Same here. MacOS, also encountered when trying it out on Kali |
Closing this because it's been stale a while and discussed in other places. |
On first installation, when running the seed data command, I get this error:
(Note: I made sure to run
docker-compose -f local.yml stop; docker-compose -f local.yml rm -f; docker-compose -f local.yml build; docker-compose -f local.yml up -d
first)Any insight as to why this might be?
The text was updated successfully, but these errors were encountered: