- integrations
- Dev Containers
- Troubleshooting
- Fix a rejected option or version
Fix a rejected option or version
The feature checks its options before it downloads anything. A bad value stops the build with exit code 2 and one ocx-feature: error: line.
Find that line below.
Every entry shows the message as the build prints it, the cause, and the fix.
For a download, checksum or platform failure, see Fix a failed feature install. Install exit codes lists every code.
Error: no ocx build for that version
ocx-feature: error: no ocx 9.9.9 build for x86_64-unknown-linux-musl in the release manifest (newest available: 0.6.8); set version: latest or distUrl to a manifest that has itThe build exits with code 2. The message above comes from version: "9.9.9".
This issue occurs when the manifest has no release with that version. The bundled manifest lists the versions released when the feature was published. A release made after the feature was published is missing from it, and so is a typo.
To fix it:
- Check the version against the ocx releases.
- For a recent release, use
version: "latest", which reads the live manifest during the build, or update the feature tag. - Without access to the live manifest, set
distUrl, as Use a version outside the baked list describes.
Error: this feature installs .tar.gz releases only
ocx-feature: error: ocx 0.4.2 ships as ocx-x86_64-unknown-linux-musl.tar.xz; this feature installs .tar.gz releases only. The oldest x86_64-unknown-linux-musl .tar.gz build is 0.4.3: set version to 0.4.3 or newerThe build exits with code 2 before any download. The message above comes from version: "0.4.2".
This issue occurs when version names an ocx release that ships in another archive format than .tar.gz.
The feature extracts .tar.gz archives only, so the first releases cannot install.
To fix it, set version to the version the message names, or to any later release.
Error: option caBundle is not a readable file
ocx-feature: error: option caBundle is not a readable file: /usr/local/share/ca-certificates/corp.pemThe build exits with code 2.
This issue occurs when caBundle names a path that does not exist inside the image at the moment the feature runs.
The option takes a path in the image, not on your machine, and not the certificate text.
Features run after the base image is built, so a Dockerfile step must copy the file first.
To fix it, copy the PEM file into the image with a COPY line in the Dockerfile that devcontainer.json builds, and use that path.
Trust the company CA during the build shows the full setup.
Error: option libc must be musl, gnu or auto
ocx-feature: error: option libc must be musl, gnu or auto (got: glibc)The build exits with code 2. The message above comes from libc: "glibc".
This issue occurs when an option value does not pass the check that runs before anything is downloaded.
The same exit code and a message of the form option <name> must be ... cover version, distUrl, mirrorUrl, managedConfig, pullGroups and the boolean options.
Two more checks have their own messages:
- A control character in a string option, such as a tab in a path:
ocx-feature: error: option ocxHome must not contain control characters. - A
managedConfigorpullGroupsvalue that starts with-:ocx-feature: error: option pullGroups must be comma-separated group names (got: -g).
Both exit with code 2. To fix it, correct the value the message names. Options lists every option with its allowed values.