#Dagger Cloud

1 messages · Page 1 of 1 (latest)

thorn mesa
#

To add to the weirdness (or maybe answer for some), it looks like the filesync tried to touch /home?? Maybe it's looking from / instead of . in some situations?
that's expected, the cache of local syncs is a lazily filled in mirror of your whole fs (otherwise we'd need separate caches for each subdir, which then defeats the purpose if there's overlapping subdirs). so for me since dagger is at /home/sipsma/github.com/sipsma/dagger, a filesync of context dir / syncs in the whole tree starting at /home

#

i do agree hitting that error when you weren't changing anything is wrong though

sinful mauve
#

huh ok, guess i just haven't seen home listed beneath the filesync span before, only saw paths relative to cwd but haven't been looking at it much at all tbh (mostly remembering marcos's screenshots)

thorn mesa
#

I feel like there might be some disagreement between client server on exclude filters or something... that would result in a situation like this (e.g. the server thinks ./cmd is actually gone whereas the client is just not sending it cause it was excluded)

#

not sure, I'll poke around

#

does it at least work on a re-run?

sinful mauve
#

yeah re-run worked fine

thorn mesa
#

personal question: do you happen to have a .gitignore in your home dir that ignores ./cmd or something?

sinful mauve
#

nope, nothing funny in home dir

proud pollen
proud pollen
#

@raw breach @warm sphinx can you remind me how crucial it is to inject ~/.docker/config.json when running CI on ns?

#

I think I remember it's a 2nd line of defense after our pull-through cache?

thorn mesa
proud pollen
#

Oh sorry wrong thread!

thorn mesa