Dagger on GCloud VM, which account / permissions

[idle plaza]

Wondering how Dagger decides what gcloud account to use and if there is a way to configure it.

I have it set to my personal accout, but it's using the service account associated with the vm

[gleaming kiln]

@idle plaza what do you mean what "gcloud account to use"?

in which context?

[idle plaza]

running dagger from the CLI on a GCP VM

our devs use cloud vms and dagger is using the service account even though the gcloud cli is configured to be (and) using their personal accounts

[gleaming kiln]

can you be more specific on "dagger is using the service account"? For what particularly? Do your dagger pipelines run some glcoud commands?

Dagger doesn't have any native gcloud integration

[idle plaza]

to push and pull images from GAR

mainly pull here, we don't actually let them push

docker is config'd to use the gcloud auth helper iirc

and does reflect gcloud auth config changes (also iirc)

[gleaming kiln]

@idle plaza dagger uses whatever config you have available in your ~/.docker/config,json to authenticate to remote registries. We don't have any native gcloud integration to push / pull images from there. So whatever credentials dagger is using, they must have been set somewhere by some helper tool

[idle plaza]

I wonder if our docker pull broke too, but no one noticed yet

[gleaming kiln]

I'd check this first

I'd assume that's the case