Update Dockerfile
Browse files- Dockerfile +2 -2
Dockerfile
CHANGED
|
@@ -26,13 +26,13 @@ COPY . .
|
|
| 26 |
# 1. Create the directories your application needs to write to at runtime.
|
| 27 |
# Using /data is a common and clean convention for persistent/writable data.
|
| 28 |
# The -p flag ensures parent directories are created if needed.
|
| 29 |
-
RUN mkdir -p /vectordb/lancedb
|
| 30 |
|
| 31 |
# 2. Change the ownership of these new data directories to be globally writable.
|
| 32 |
# The 777 permission is broad, but very effective in hosted environments where
|
| 33 |
# you don't know which user ID (e.g., uid=1000) will run the process.
|
| 34 |
# This command says "any user can read, write, and execute in these folders".
|
| 35 |
-
RUN chmod -R 777 /vectordb
|
| 36 |
|
| 37 |
# --- END: PERMISSION FIXES ---
|
| 38 |
|
|
|
|
| 26 |
# 1. Create the directories your application needs to write to at runtime.
|
| 27 |
# Using /data is a common and clean convention for persistent/writable data.
|
| 28 |
# The -p flag ensures parent directories are created if needed.
|
| 29 |
+
RUN mkdir -p /app/vectordb/lancedb
|
| 30 |
|
| 31 |
# 2. Change the ownership of these new data directories to be globally writable.
|
| 32 |
# The 777 permission is broad, but very effective in hosted environments where
|
| 33 |
# you don't know which user ID (e.g., uid=1000) will run the process.
|
| 34 |
# This command says "any user can read, write, and execute in these folders".
|
| 35 |
+
RUN chmod -R 777 /app/vectordb
|
| 36 |
|
| 37 |
# --- END: PERMISSION FIXES ---
|
| 38 |
|