OpenShift环境下Django多SQLite3数据库配置问题咨询

Hey there, let’s tackle this SQLite multi-database issue on OpenShift together! The core problem here boils down to OpenShift’s container environment constraints—specifically its ephemeral filesystem and strict permission rules—that your local setup doesn’t have to deal with. Here’s how to fix it:

Local relative paths like db1.sqlite3 won’t work reliably on OpenShift because most container directories are either read-only or get wiped when the pod restarts. You need to store all SQLite files in a persistent, writable directory that OpenShift allows.

Update your settings.py to use a dedicated data directory, preferably one tied to an environment variable for flexibility:

import os
from pathlib import Path

BASE_DIR = Path(__file__).resolve().parent.parent

# Use OpenShift's default writable persistent directory, or fallback locally
DATA_DIR = Path(os.environ.get("DATA_DIR", BASE_DIR / "persistent_data"))
# Create the directory if it doesn't exist to avoid startup errors
DATA_DIR.mkdir(parents=True, exist_ok=True)

DATABASES = {
    "default": {
        "ENGINE": "django.db.backends.sqlite3",
        "NAME": DATA_DIR / "default_db.sqlite3",
    },
    "db2": {
        "ENGINE": "django.db.backends.sqlite3",
        "NAME": DATA_DIR / "second_db.sqlite3",
    },
    "db3": {
        "ENGINE": "django.db.backends.sqlite3",
        "NAME": DATA_DIR / "third_db.sqlite3",
    }
}

Even with the right path, your database files will still disappear when the pod restarts unless you mount a persistent volume. Here’s how to set this up:

• Log into your OpenShift console, navigate to your project.
• Go to Storage > Persistent Volume Claims and create a new PVC (choose a storage class, set a size that fits your needs).
• Open your app’s Deployment configuration, add a Volume Mount:
  • Mount path: /opt/app-root/data (match the DATA_DIR environment variable we’ll set next)
  • Associate it with the PVC you just created.
• Add an environment variable to your Deployment: DATA_DIR=/opt/app-root/data

OpenShift runs pods as a non-root user (usually UID 1001), so the data directory needs to be writable by this user. Add these lines to your Dockerfile to set permissions during build:

# Assuming you're using a Python base image
FROM python:3.11-slim

WORKDIR /opt/app-root/src

# Create persistent data dir and set ownership for OpenShift's non-root user
RUN mkdir -p /opt/app-root/data && chown -R 1001:0 /opt/app-root/data

# Rest of your Dockerfile steps (install dependencies, copy code, etc.)
USER 1001

After deploying, you need to make sure migrations are applied to every database. You can do this by opening a terminal in your pod and running:

python manage.py migrate --database=default
python manage.py migrate --database=db2
python manage.py migrate --database=db3

For future deployments, you can add these commands to a startup script (with a check to avoid redundant runs) to automate this step.

If you still see server errors, check your pod’s logs—they’ll tell you exactly what’s wrong (e.g., "permission denied" or "no such file or directory"). You can view logs via the OpenShift console, or run this command in your local terminal:

oc logs <your-pod-name>

Use the log details to tweak paths, permissions, or PVC settings as needed.

内容的提问来源于stack exchange，提问作者M Hussain