https://blue-build.org/ logo
Adding large files to an image via Git LFS
# questions
j
I have been working on a custom image, and want to drop a bunch of my favorite hi-res images into
/usr/share/wallpapers
. So I put them in my repo with a
files
module and committed them using Git LFS to avoid directly committing large binaries. However, when I run my build, Blue Build just writes the symbolic link for each large file into the wallpapers directory instead of the actual file. I tried setting up LFS in my image using a
script
module , and have considered writing a custom module to handle LFS. But it seems that, because module seem to run within the context of a Containerfile, it does not recognize that it is even in a Git repo. Do you have any suggestions for how to go about this? Or should I just put my wallpaper files in a bucket and download them at build time?
a
message has been deleted
g
[This thread](https://github.com/moby/moby/issues/40449#issuecomment-1545819389) might be able to help you. You can also make use of the [copy](https://blue-build.org/reference/modules/copy/) module if you need
x
the checkout action requires
lfs: true
to be set for lfs files to be fetched
this is not set by the checkout action included by default in the bluebuild action
you can set the bluebuild action to skip checkout and do it yourself in a previous build step
if you're using github, of course
g
Ah this sounds more true
j
ahh thank you. I'll try this!
I was reading the
bluebuild
source to see if it needed to happen there, but the GitHub action makes way more sense.
4 Views