Ask questionsUSABILITY: Make a missing task image/image_resource have a better error message

Bug Report

When creating a task whose image or image_resource has been omitted, the error message is not useful:

Backend error: Exit status: 500, message: {"Type":"","Message":"runc exec: exit status 1: exec failed: container_linux.go:348: starting container process caused \"no such file or directory\"\n","Handle":"","ProcessID":"","Binary":""}

This is hard to determine whether or not the error is a missing an image or the task definition itself is missing.

Steps to Reproduce

  1. Create a task in a pipeline whose image_resource or image field is missing
  2. ???
  3. Profit!

Expected Results

  1. A useful error message that no image was available

Actual Results

  1. A not useful error message that file was not found

Version Info

  • Concourse version: 4.2.1
  • Deployment type (BOSH/Docker/binary): BOSH
  • Infrastructure/IaaS: vSphere
  • Browser (if applicable):
  • Did this used to work? Probably not ¯\(ツ)/¯?

Answer questions edtan

Perhaps we can check this at the client side in fly first when they create the pipeline?

Github User Rank List