No projects found when running inside a container, works fine on the host

Asked 21 Apr 20261,690 views2 answers

8votes

Same repo, mounted into the image at /srv/app. On the host every command is fine. Inside:

text

✖ PROJECT_NOT_FOUND: No projects found.
  hint: Run `sdods project create <slug>`.

And naming one explicitly gives a slightly different message:

text

✖ PROJECT_NOT_FOUND: Unknown project "demo-shop".
  hint: No projects found under /srv/app/projects. Run `sdods project create <slug>`.

The directory is definitely there — ls /srv/app/projects shows all three.

asked by Paulo Mendes97 · 21 Apr 2026

2 answers

12votes✓
Accepted answer
The second message names the directory it looked in, and that is the thing to trust: /srv/app/projects. If the folders are there and it found none, the projects were skipped rather than missed — each one needs a sdods.project.yaml directly inside it.
Most likely your mount is not bringing the files in, only the directory names, or the working directory is not where you think. The repo root is found by walking up from the current directory looking for sdods.config.ts, sdods.config.json or sdods.workspace.yaml, or for a projects/ directory next to a package.json. A container whose workdir is / will walk up from there and find nothing.
bash
```
ls /srv/app/projects/demo-shop/sdods.project.yaml
```
If the layout is unusual, name the directory outright:
bash
```
SDODS_PROJECTS_DIR=/srv/app/projects sdods project list
```
answered by Reeta Nandalmaintainer41,280 · 21 Apr 2026
7votes
Set the working directory to the repo root in the container and this stops being a special case — everything below it then resolves the same way it does on your machine.
Also check the mount is the repo root and not projects/ itself. Mounting the inner directory gets you the project folders with no sdods.workspace.yaml above them, which changes where the root walk stops.
answered by Daniel Oyelaranmaintainer24,177 · 22 Apr 2026

Have a different question? Ask it.