"failed to create volume" error when running pipelines

When I attempt to run my pipeline, it fails and the error “failed to create volume” is displayed in the UI. This is running in a Kubernetes environment.

The relevant logs are below:

{
  "timestamp": "2019-07-04T12:35:32.161741400Z",
  "level": "info",
  "source": "baggageclaim",
  "message": "baggageclaim.api.volume-server.get-volume.get-volume.volume-not-found",
  "data": {
    "session": "3.1.258.1",
    "volume": "a43c5795-bf8b-45a4-7cb9-454655bbe902"
  }
}
{
  "timestamp": "2019-07-04T12:35:32.161828700Z",
  "level": "info",
  "source": "baggageclaim",
  "message": "baggageclaim.api.volume-server.get-volume.volume-not-found",
  "data": {
    "session": "3.1.258",
    "volume": "a43c5795-bf8b-45a4-7cb9-454655bbe902"
  }
}
{
  "timestamp": "2019-07-04T12:35:32.165813000Z",
  "level": "error",
  "source": "baggageclaim",
  "message": "baggageclaim.api.volume-server.create-volume-async.create-volume.failed-to-materialize-strategy",
  "data": {
    "error": "invalid argument",
    "handle": "a43c5795-bf8b-45a4-7cb9-454655bbe902",
    "session": "3.1.259.1"
  }
}
{
  "timestamp": "2019-07-04T12:35:32.165871000Z",
  "level": "error",
  "source": "baggageclaim",
  "message": "baggageclaim.api.volume-server.create-volume-async.failed-to-create",
  "data": {
    "error": "invalid argument",
    "handle": "a43c5795-bf8b-45a4-7cb9-454655bbe902",
    "privileged": false,
    "session": "3.1.259",
    "strategy": {
      "type": "cow",
      "volume": "a7ba32d3-bb75-4711-7211-f0b171ed70ff"
    }
  }
}

Facing same issue, Let me know if you resolved it. Thanks!

Setting CONCOURSE_BAGGAGECLAIM_DRIVER=naive fixed this issue for me.

I know very little about what this option does or any consequence of changing it. I came upon a thread elsewhere that suggested it.

could it be simply lack of disk space which went away?
if I change my cicd containers a few times, concourse seems to keep the old ones hanging around which uses up disk space. so I end up landing down each worker in turn, pruning them, then removing the entire concourse worker space and rebooting. then it only downloads the containers which it needs and thus frees up disk space.

I would suggest inspecting your docker volumes space used up. I tend to be faced with similar issues every once and a while when my volume space is occupied. A simple docker system df -v will give you a better idea of the amount of space used.