Closed jonfroehlich closed 6 years ago
Simple fix: navigate to the migrations directory in django and delete all of the migrations. Django migrations have dependencies that point to the previous one applied, so by deleting them all you force Django to remake all the migrations and thus remove the faulty dependency
Do you mean navigate to migrations dir in Docker?
Sent from my iPhone
On Aug 11, 2018, at 1:27 PM, johnsonkuang notifications@github.com wrote:
Simple fix: navigate to the migrations directory in django and delete all of the migrations. Django migrations have dependencies that point to the previous one applied, so by deleting them all you force Django to remake all the migrations and thus remove the faulty dependency
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
No just go to the local migrations directory that you’re using and then delete all the migration files. That will do it.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Jon Froehlich notifications@github.com Sent: Saturday, August 11, 2018 4:04:39 PM To: jonfroehlich/makeabilitylabwebsite Cc: johnsonkuang; Assign Subject: Re: [jonfroehlich/makeabilitylabwebsite] I can no longer get my Docker instance to run the ML website (#555)
Do you mean navigate to migrations dir in Docker?
Sent from my iPhone
On Aug 11, 2018, at 1:27 PM, johnsonkuang notifications@github.com wrote:
Simple fix: navigate to the migrations directory in django and delete all of the migrations. Django migrations have dependencies that point to the previous one applied, so by deleting them all you force Django to remake all the migrations and thus remove the faulty dependency
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/jonfroehlich/makeabilitylabwebsite/issues/555#issuecomment-412307226, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfdHHDkilL4c2mhbdOVVV1nK8yihM3AQks5uP2MHgaJpZM4V4584.
@jonfroehlich did the solution work?
I likely won't have time to work on the ML website this week. Will let you know, however.
I deleted all files in the migrations folder and tried again (first rebuilding docker via docker build . -t makelab_image
and then running docker, see command below). This is the error I got:
PS D:\Git\makeabilitylabwebsite> docker run -p 8000:8000 -ti -v ${pwd}/db:/code/db -v ${pwd}/media:/code/media -v ${pwd}/website:/code/website makelab_image
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: error while creating mount source path '/host_mnt/d/Git/makeabilitylabwebsite/db': mkdir /host_mnt/d: file exists.
Hmm, try rebuilding the docker image, maybe that will resolve this issue
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Jon Froehlich notifications@github.com Sent: Monday, August 13, 2018 1:20:27 PM To: jonfroehlich/makeabilitylabwebsite Cc: johnsonkuang; Assign Subject: Re: [jonfroehlich/makeabilitylabwebsite] I can no longer get my Docker instance to run the ML website (#555)
I deleted all files in the migrations folder and tried again. This is the error I got:
PS D:\Git\makeabilitylabwebsite> docker run -p 8000:8000 -ti -v ${pwd}/db:/code/db -v ${pwd}/media:/code/media -v ${pwd}/website:/code/website makelab_image C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: error while creating mount source path '/host_mnt/d/Git/makeabilitylabwebsite/db': mkdir /host_mnt/d: file exists.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/jonfroehlich/makeabilitylabwebsite/issues/555#issuecomment-412649924, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfdHHDYmztGzcL1FvU3mGQeMZlmTYV-fks5uQd-LgaJpZM4V4584.
Isn't that what I did? Re-read my message.
In the end, I just started from scratch :(
Looks like it has something to do with @johnsonkuang's get_person stuff that he was working on...
Should I just start over with a clean instance of Docker and code? Here's the full log.