Concourse: Cryptic error at start of task: container_linux.go:348: starting container process caused
Bug Report
Upon start of one of the ci tasks in the pipeline, the following error occurred and terminated the execution of the pipeline:
Backend error: Exit status: 500, message: {"Type":"","Message":"runc exec: exit status 1: exec failed: container_linux.go:348: starting container process caused \"exec format error\"\n","Handle":"","ProcessID":"","Binary":""}
As i couldn't find the cause of the error for now, i cannot give a description on how to
reproduce. I will post further results if i find out where the problem resides.
The task probably has some misconfiguration as i run it the first time.
Actual Results
Pipeline terminated with error.
Version Info
- Concourse version: 4.2.1
- Deployment type (BOSH/Docker/binary): BOSH Cluster
- Infrastructure/IaaS: vSphere
- Browser (if applicable): Chrome
gdenn
👍9
Related issues
Templarian
路
3Comments
kcmannem
路
3Comments
evanchaoli
路
3Comments
UmamaheshMaxwell
路
3Comments
drahnr
路
3Comments
Most helpful comment
The problem was that there was neither a shebang in the script that is called specified nor a binary to run the script.
It would be nice if this error would be handled by the worker and a more descriptive error message would be displayed to the user.
E.g. "Backend error: no binary specified for the execution of
All 3 comments
The problem was that there was neither a shebang in the script that is called specified nor a binary to run the script.
It would be nice if this error would be handled by the worker and a more descriptive error message would be displayed to the user.
E.g. "Backend error: no binary specified for the execution of