You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this one, since it's not actually an R package, probably not. but in general, the .Xignore files, such as .Rbuildignore and .dockerignore can have huge impacts on build processes. (I'm annoyed that they're dotfiles).
As a quick example, .dockerignore excludes files from the docker build context, which means that when you have a line like this (currently on main):
if you don't have a .dockerignore defined, everything in the build context gets pulled into the image, which means that if you happen to have a copy of the rawdata inputs and outputs in the same directory, those get added. As does the .git directory, meaning that ever time you commit, you're invalidating the cache (and these problems multiply each other).
closes#128
based on
https://github.com/RMI-PACTA/workflow.pacta/blob/main/.dockerignore with
the following differences
- allowing markdown files because I think it is reasonably relevant to
have the license and README markdown files baked into the image along
with the associated code
- excluding the `docker-compose.yml` because that's not relevant inside
the image (and I wonder if in some cases it could be a security concern,
e.g. if one did not want local path specifications to be revealed inside
the image)
---------
Co-authored-by: Alex Axthelm <[email protected]>
Originally posted by @AlexAxthelm in #117 (comment)
https://docs.docker.com/build/building/context/#dockerignore-files
The text was updated successfully, but these errors were encountered: