Difference between Quickstart and Standard Mode

What is the difference between the “quickstart” invocation and the “web”+“worker” invocation of concourse? They seem to have different behaviors with respect to checking resources.

For context, I’m trying to migrate from the docker-compose “quickstart” concourse to a full install (have tried single machine and separate web/worker machines). I’m using v6.1.0 for both, and I load the same pipeline file to both. The docker-compose quickstart distribution successfully checks the resources, but the full install version chokes on checking the resources. It complains:

run check step: run check step: check: resource script ‘/opt/resource/check []’ failed: exit status 128

stderr:
Identity added: /tmp/git-resource-private-key (concourse)
Cloning into ‘/tmp/git-resource-repo-cache’…
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I know the repo exists, and I know that I have the correct keys and such, because the exact same pipeline file runs without a problem on the docker-compose quickstart version. Also, the worker on the full version was invoked via sudo. So I’m assuming there isn’t a problem with the worker launching the docker containers. Any thoughts? I’ve been stumped on this for a while now… :slight_smile:

1 Like