You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ensure that the `commands.json` file exists. remove the mount if you want use the commands.json from the repository (https://github.com/danielraab/command-builder/blob/master/public/commands.json).
Then access the application at `http://localhost:3000`
@@ -138,6 +126,36 @@ The final image is based on `nginx:alpine`, providing a minimal footprint optimi
138
126
139
127
## Troubleshooting
140
128
129
+
### File mount error: "not a directory"
130
+
131
+
If you see an error like:
132
+
```
133
+
docker: Error response from daemon: failed to create task for container: OCI runtime create failed:
134
+
unable to start container process: error mounting "/path/to/commands.json" to rootfs: not a directory
135
+
```
136
+
137
+
**Cause**: Docker requires that the source file exists on the host before mounting. If the file doesn't exist, Docker creates a directory instead, causing the mount to fail.
138
+
139
+
**Solution**: Ensure the `public/commands.json` file exists before starting the container:
140
+
141
+
```bash
142
+
# From the project root
143
+
ls -la public/commands.json
144
+
145
+
# If the file doesn't exist, copy it from the repository
146
+
# Or create it with proper content
147
+
```
148
+
149
+
When running from a different directory, use absolute paths:
0 commit comments