FAQ
Frequently asked questions, common errors and solutions.
Pipeline fails with /bin/sh: no such file or directory error
Full error:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown
Potential causes:
The container defined in the step does not contain /bin/sh
.
Solutions:
Publish a new version of the container that has /bin/sh
, or switch to a different container that already has /bin/sh
.
Pipeline fails with resource is denied error
Full error:
Error response from daemon: pull access denied for IMAGE_NAME, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Potential causes:
- The container defined in the step does not exist
- The container defined in the step is private, and requires authentication
Solutions:
- Verify the container exists and can be pulled by running
docker pull IMAGE_NAME
locally - Gitness inherits authentication from the host, see Docker's login command documentation
Pipeline step fails with /bin/sh: exec format error
Full error:
exec /bin/sh: exec format error
Potential causes:
The container defined in the step is for a different OS and/or architecture.
Solutions:
Switch to a container supported by your machine (see Docker's Multi-platform images documentation).