#qq - how do I enable git lfs support
1 messages · Page 1 of 1 (latest)
Hi! 👋 What's your use case look like?
I looked up your question in ChatGPT and saw some helpful suggestions to install the git-lfs package and to exec git lfs install and then git lfs pull --include "mybigfile" once you've cloned a repo.
That's easy to do with Dagger, if that sequence does what you need.
I'd think you'd need sufficient resources to handle the large files, but otherwise, I don't see any barrier.
Others may know caveats.
If you're cloning first,
you'll want to use filters as well https://docs.dagger.io/api/filters/
When you pass a directory to a Dagger Function as argument, Dagger uploads everything in that directory tree to the Dagger Engine. For large monorepos or directories containing large-sized files, this can significantly slow down your Dagger Function while filesystem contents are transferred. To mitigate this problem, Dagger lets you apply filter...
For container-use specifically, it's possible we need some options to enable it in the git operations under the hood. I'll look into it!
Good point @lunar dome let us know if you're using https://dagger/container-use or https://dagger/dagger for your project.
I realize the name of this channel might be confusing for folks looking for "how to use containers"
hey - thanks for answering. I'm trying out container-use in a game codebase that uses git lfs for assets, and its failing with "smudge filter lfs failed" when trying to check out the assets