Unable to seed database about ghostwriter

[CicadaMikoto]

I am also having this issue and it is preventing installation. Any ETA for a fix or a workaround?

[c4ch3c4d3]

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 RUN chmod +x /seed_data to RUN chmod 777 /seed_data. Without granting global permissions, I would continuously get a /bin/ash: can't open '/seed_data': Permission denied when running docker-compose -f production.yml run --rm django /seed_data.

[c4ch3c4d3]

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.

[chrismaddalena]

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.

[jimmio]

I was on macOS when I encountered the issue, and I did not customize the database or input data before seeding.

[deletehead]

Same here. MacOS, also encountered when trying it out on Kali

[chrismaddalena]

Closing this because it's been stale a while and discussed in other places.