devcontainer build failure
Open
@aristarkhovNV is already working on this.
Since Feb 1, 2026.
- Dominant language
- Python
- Stars
- 385
- Forks
- 88
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 82
Description
Turns out ghcr.io/devcontainers-extra/features can get rate limited easily.
13.99 urllib.error.HTTPError: HTTP Error 403: rate limit exceeded
14.19 Traceback (most recent call last):
14.19 File "<string>", line 1, in <module>
14.19 File "nanolayer.__main__", line 50, in main
14.19 File "typer.main", line 328, in __call__
14.19 File "typer.main", line 311, in __call__
14.19 File "click.core", line 1157, in __call__
14.19 File "typer.core", line 778, in main
14.19 File "typer.core", line 216, in _main
14.19 File "click.core", line 1688, in invoke
14.19 File "click.core", line 1688, in invoke
14.19 File "click.core", line 1434, in invoke
14.19 File "click.core", line 783, in invoke
14.19 File "typer.main", line 683, in wrapper
14.19 File "nanolayer.cli.install", line 66, in install_devcontainer_feature
14.19 File "nanolayer.installers.devcontainer_feature.oci_feature_installer", line 134, in install
14.19 File "nanolayer.utils.invoker", line 59, in invoke
14.19 nanolayer.utils.invoker.Invoker.InvokerException: The command 'cd /tmp/tmp7mdm8z06 && chmod +x -R . && _REMOTE_USER="root" _REMOTE_USER_HOME="/root" REPO="astral-sh/uv" BINARYNAMES="uv,uvx" ASSETREGEX="^uv-x86_64-unknown-linux-gnu\.tar\.gz$" VERSION="latest" LIBNAME="uv" RELEASETAGREGEX="" BINLOCATION="/usr/local/bin" LIBLOCATION="/usr/local/lib" ADDITIONALFLAGS="" NANOLAYER_VERBOSE="" NANOLAYER_FORCE_CLI_INSTALLATION="" NANOLAYER_PROPAGATE_CLI_LOCATION="1" NANOLAYER_CLI_LOCATION="/tmp/nanolayer-cRZdirBxMT/nanolayer" bash -i +H ./install.sh' failed. error: Return Code: 1. see logs for details.
14.29 ERROR: Feature "uv (via GitHub Releases)" (ghcr.io/devcontainers-extra/features/uv) failed to install! Look at the documentation at http://github.com/devcontainers-extra/features/tree/main/src/uv for help troubleshooting this error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.