[Bug]: can't start supebase-db

[georgeqin96]

What happened?

@dosubot A bug happened! when I run docker compose -f docker-compose-ollama.yml up --build
2023-12-12 20:22:35 2023-12-12 12:22:35.652 UTC [38] FATAL: could not create file "base/1/2753_fsm": Input/output error
2023-12-12 20:22:35 2023-12-12 12:22:35.652 UTC [38] PANIC: cannot abort transaction 1, it was already committed
2023-12-12 20:22:35 Aborted
2023-12-12 20:22:35 child process exited with exit code 134
2023-12-12 20:22:35 initdb: removing contents of data directory "/var/lib/postgresql/data"
2023-12-12 20:22:35 running bootstrap script ...

what happen?

Relevant log output

No response

Twitter / LinkedIn details

No response

[dosubot]

🤖

Hey there @georgeqin96! Good to see you again, seems like we're getting really good at this bug squashing dance, huh? 🕺

Based on the error message you provided, it seems like there might be an issue with the file system permissions, network timeout, disk space, or Docker version compatibility.

Here are a few potential solutions based on similar issues in the Quivr repository:

1. Change Line Endings: In a previous issue, it was suggested to change the line endings from CRLF to LF for the backend/scripts/start.sh file and rebuild the Docker image. This can be done using the command docker compose build --no-cache or docker compose up --build.

2. Check .env Files: Another issue suggested using the same keys in both front and back-ends .env files.

3. Check Network Timeout: The yarn install command in the Dockerfile has a network timeout set to 1000000 milliseconds (or 1000 seconds). If your network is slow or unstable, it might be causing the installation to timeout, leading to the error. You can try increasing the timeout or improving your network connection.

4. Check File System Permissions: Docker might not have the necessary permissions to access certain files or directories. This could be causing the "Input/output error". You can try running Docker with sudo or checking the permissions of the files and directories Docker is trying to access.

5. Check Disk Space: If your system is running out of disk space, Docker might not be able to build the image, leading to the error. You can try freeing up some disk space and then retrying.

6. Check Docker Version: You're using Docker Compose version 3.8. There might be compatibility issues with this version and the commands or configurations in the Dockerfile. You can try updating Docker to the latest version and then retrying.

If none of these solutions work, could you please provide more details about the error message and your system setup? This will help in diagnosing the issue further.

Sources

• Error with Docker compose for backend
• Installation issue
• cms/quivr/Dockerfile
• docker-compose.dev.yml

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.