Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Same repo, mounted into the image at /srv/app. On the host every command is fine. Inside:
✖ PROJECT_NOT_FOUND: No projects found.
hint: Run `sdods project create <slug>`.And naming one explicitly gives a slightly different message:
✖ 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.
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.
ls /srv/app/projects/demo-shop/sdods.project.yamlIf the layout is unusual, name the directory outright:
SDODS_PROJECTS_DIR=/srv/app/projects sdods project listSet 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.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.