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.
Our build network can only reach an internal registry mirror. The installer stops before it downloads anything:
@sdods/cli is not available on the npm registry.
Check your registry and network, or install from source with: --source git
Docs: https://docs.sdods.com/docs/getting-started/installation/Exit code 7. The package resolves fine from my laptop, so I assume the mirror has not pulled it through yet. Is there a way to confirm that rather than guess?
Accepted answer
Confirm it directly — the installer is asking the registry your environment points at, so ask it the same question yourself:
npm view @sdods/cli version --registry "$(npm config get registry)"If that fails, the mirror is the problem and nothing about SDODS will fix it. Most proxying registries only fetch a package on first request and some need it allow-listed first.
Note which message you got, because there are two and they mean different things:
--source npm, where you told it not to consider anything else.auto path, and that one is usually temporary — retry before doing anything else.auto never falls back to a clone on its own. A registry outage should say so rather than hand you a 1.5 GB source tree you did not ask for.
For the build itself, do not install from the network on every job. Install once when you bake the image — the install is the slow, flaky step in that pipeline and it does not change between commits.
SDODS_HOME=/opt/sdods SDODS_BIN_DIR=/usr/local/bin SDODS_BROWSERS=chromium SDODS_YES=1 \
sh -c "curl -fsSL https://sdods.com/install.sh | sh"Every flag has an environment variable equivalent, which is what keeps that layer readable and cacheable.
More on shaping this for CI in Guides → Sharding and CI.
We hit this exact thing and it was the mirror. Ours only mirrors scopes that have been requested through the UI once, so @sdods did not exist until someone asked for it. Took a day, then the ordinary one-liner worked with no flags.
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.