#How to use DO_NOT_TRACK with dagger

1 messages · Page 1 of 1 (latest)

zenith lily
#

I am trying to set DO_NOT_TRACK=1 in cmd line where I am running dagger, but I still see traces in the cloud. How can I disable those?

#

I also tried SHUTUP=1 and other env variables, but that has no impact either.

stuck agate
#

Hey, @zenith lily
Are you connected to dagger cloud from dagger login?

zenith lily
#

yeah I am. and I did verify if I logout, it does not send traces anymore. but I was hoping there is an env variable or config to disable for one tool (think of it like a private repo), while I can keep it for another tool (vs public repo).

burnt token
zenith lily
#

hey Marcos 👋 , let me try that. thanks

#

hmm, that didn't help. I may be doing something incorrectly, i will come back to this later in the day and try again.

burnt token
burnt token
#

@zenith lily just checked that a quick way to bypass this is by setting XDG_CONFIG_HOME to a bogus directory. i.e: XDG_CONFIG_HOME=/tmp/foo dagger call.. won't read any dagger config files

zenith lily
#

👍 thank you very much for checking this out Marcos. I will try this out and let you know.