Hello All, I am trying to configure pants to work with remote execution, and have configured buildbarn remote execution. Although when build my package with the remote store configured I am getting the following error. Exception: InvalidArgument: "Failed to obtain offset store for instance \"main\": Unknown instance name" Can anyone direct me how to debug this issue? I think I am using the wrong remote_instance_name but I am not sure what that value should be set to.

You might use this wonderful resource: https://remote-apis-testing.gitlab.io/remote-apis-testing/ You'll note the elements you care about are green in that grid. The Pants config is here: https://gitlab.com/remote-apis-testing/remote-apis-testing/-/blob/master/docker-compose-templates/docker-compose-pants.jinja2_template And build barn config here: https://gitlab.com/remote-apis-testing/remote-apis-testing/-/blob/master/docker-compose-templates/docker-compose-buildbarn.jinja2_template Hopefully that points out things you have set up differently which leads to a fix. Beyond that I'm buildbarn ignorant.

What did you set

instanceNamePrefix

to be for the runners? Pants is looking for runners with the name

main

which probably don't exists. https://github.com/buildbarn/bb-remote-execution/blob/master/pkg/proto/remoteworker/remoteworker.proto#L54

I'm not sure. If you dig into the gitlab project linked above you should find the buildbarn image used and configs: + https://gitlab.com/remote-apis-testing/remote-apis-testing/-/blob/master/matrix.yml#L115 + https://gitlab.com/remote-apis-testing/remote-apis-testing/-/tree/master/docker-compose/buildbarn_config

Thanks I've gotten a step further. Now I'm getting the exception: No workers exist for instance "remote-execution" platform {"properties": [{'name':'OSFamily', 'value': ''Linux'}]} This is the configuration I have for the workers

{
      blobstore: common.blobstore,
      maximumMessageSizeBytes: common.maximumMessageSizeBytes,
      scheduler: { address: 'scheduler:8983' },
      httpListenAddress: common.httpListenAddress,
      maximumMemoryCachedDirectories: 1000,
      instanceName: 'remote-execution',
      browserUrl: common.browserUrl,
      buildDirectories: [{
        native: {
          buildDirectoryPath: '/worker/build',
          cacheDirectoryPath: '/worker/cache',
          maximumCacheFileCount: 10000,
          maximumCacheSizeBytes: 1024 * 1024 * 1024,
          cacheReplacementPolicy: 'LEAST_RECENTLY_USED',
        },
        runners: [{
          endpoint: { address: 'unix:///worker/runner' },
          concurrency: 8,
          platform: {
            properties: [
              { name: 'OSFamily', value: 'Linux' },
              { name: 'container-image', value: '<docker://marketplace.gcr.io/google/rbe-ubuntu16-04@sha256:b516a2d69537cb40a7c6a7d92d0008abb29fba8725243772bdaf2c83f1be2272>' },
            ],
          },
          defaultExecutionTimeout: '1800s',
          maximumExecutionTimeout: '3600s',
          workerId: {
            'pod': std.extVar("POD_NAME"),
            'node': std.extVar("NODE_NAME")
          },
        }],
      }],
    }

I recall that Buildbarn needs an exact match between the platform properties sent by Pants and the worker’s configured platform properties. In that config, the

container-image

property is defined on the worker and is not being sent by Pants.

spot on! thanks @fast-nail-55400

Tangentially, are you aware of the #buildbarn channel on BuildTeamWorld Slack?

Are these question better to ask over there? @fast-nail-55400

Not necessarily. Just mentioning it so you are aware of it since they will have deeper knowledge and experience with Buildbarn because that is where the Buildbarn developers hang out. You probably want to ask in whichever channel can answer the question. 🙂 Pants and some basic Buildbarn here, and deeper Buildbarn questions over there.

for that piece I could probably configure a multi-read/write volume for the docker cache that is mounted on all the workers