get base database up and running again #22

Closed
opened 4 years ago by youainti · 3 comments
youainti commented 4 years ago (Migrated from gitea.kgjk.icu)

Tried to restart the database. It errored out.

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/will/research/ClinicalTrialsDataProcessing/AACT_downloader/20220201_clinical_trials/postgres_data.dmp" to rootfs at "/mnt/host_data/postgres_data.dmp": mount /home/will/research/ClinicalTrialsDataProcessing/AACT_downloader/20220201_clinical_trials/postgres_data.dmp:/mnt/host_data/postgres_data.dmp (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Error: failed to start containers: 9df0

I need to get this database back up.

Tried to restart the database. It errored out. > Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/will/research/ClinicalTrialsDataProcessing/AACT_downloader/20220201_clinical_trials/postgres_data.dmp" to rootfs at "/mnt/host_data/postgres_data.dmp": mount /home/will/research/ClinicalTrialsDataProcessing/AACT_downloader/20220201_clinical_trials/postgres_data.dmp:/mnt/host_data/postgres_data.dmp (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type Error: failed to start containers: 9df0 I need to get this database back up.
youainti commented 3 years ago (Migrated from gitea.kgjk.icu)

Got it running. THe issue was that it required running the docker-compose.yaml from the submodule not the original directory. I removed the original directory to remove the confusion.

Got it running. THe issue was that it required running the `docker-compose.yaml` from the submodule not the original directory. I removed the original directory to remove the confusion.
youainti commented 3 years ago (Migrated from gitea.kgjk.icu)

Running with old data.

Running with old data.
youainti commented 3 years ago (Migrated from gitea.kgjk.icu)

wrote a justfile to setup the data again. it worked just fine.

wrote a justfile to setup the data again. it worked just fine.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: youainti/ClinicalTrialsDataProcessing#22
Loading…
There is no content yet.