How do I tar a directory of files and folders without including the directory itself?
What if I just want to include everything (including any hidden system files) in my_directory, but not the directory itself? I don’t want:
my_directory --- my_file --- my_file --- my_file Is that the default behavior of doing tar -czf ? In my case it’s only storing the files and not the directory. When I just tar the directory it includes it but with tar -czf it is only adding the files.
22 Answers 22
tar -czvf my_directory.tar.gz -C my_directory . The -C my_directory tells tar to change the current directory to my_directory , and then . means «add the entire current directory» (including hidden files and sub-directories).
Make sure you do -C my_directory before you do . or else you’ll get the files in the current directory.
Warning: you’ll get entries as ./file-name.ext instead of file-name.ext !
If you need entries in the form of file-name.ext , read other answers.
«Unlike most options, -C is processed at the point it occurs within the list of files to be processed. Consider the following command: tar —create —file=foo.tar -C /etc passwd hosts -C /lib libc.a » apl.jhu.edu/Misc/Unix-info/tar/tar_65.html I always try tar -czvf my_directory.tar.gz * -C my_directory and that does not work. -C location is important! Damn tar.
Not perfect — tar file contains ‘.’ and also ./file1 instead of just file1. I like the solution by mateusza below to use —strip-components when un-tarring.
cd my_directory/ && tar -zcvf ../my_dir.tgz . && cd - should do the job in one line. It works well for hidden files as well. «*» doesn’t expand hidden files by path name expansion at least in bash. Below is my experiment:
$ mkdir my_directory $ touch my_directory/file1 $ touch my_directory/file2 $ touch my_directory/.hiddenfile1 $ touch my_directory/.hiddenfile2 $ cd my_directory/ && tar -zcvf ../my_dir.tgz . && cd .. ./ ./file1 ./file2 ./.hiddenfile1 ./.hiddenfile2 $ tar ztf my_dir.tgz ./ ./file1 ./file2 ./.hiddenfile1 ./.hiddenfile2 Not perfect — tar file contains ‘.’ and also ./file1 instead of just file1. I like the solution by mateusza below to use —strip-components when un-tarring.
@Ivan if you replace . with * so the command will be cd my_directory/ && tar -zcvf ../my_dir.tgz * && cd .. then it will work as you expected.
@jmathew You can also use a subshell so your current shell’s working directory doesn’t change: $ (cd my_directory/ && tar -zcvf ../my_dir.tgz .)
You can also create archive as usual and extract it with:
tar --strip-components 1 -xvf my_directory.tar.gz This solution is especially good in situations where you are working with tarballs created before all of your requirements were known.
If the creation of tar is on my side but the extraction is not and expects no . as root dir, this will not solve the problem.
TL;DR (no ./ and no ./file1 !)
find /my/dir/ -printf "%P\n" | tar -czf mydir.tgz --no-recursion -C /my/dir/ -T - With some conditions (archive only files, dirs and symlinks):
find /my/dir/ -printf "%P\n" -type f -o -type l -o -type d | tar -czf mydir.tgz --no-recursion -C /my/dir/ -T - Explanation
The below unfortunately includes a parent directory ./ in the archive:
You can move all the files out of that directory by using the —transform configuration option, but that doesn’t get rid of the . directory itself. It becomes increasingly difficult to tame the command.
You could use $(find . ) to add a file list to the command (like in magnus’ answer), but that potentially causes a «file list too long» error. The best way is to combine it with tar’s -T option, like this:
find /my/dir/ -printf "%P\n" -type f -o -type l -o -type d | tar -czf mydir.tgz --no-recursion -C /my/dir/ -T - Basically what it does is list all files ( -type f ), links ( -type l ) and subdirectories ( -type d ) under your directory, make all filenames relative using -printf «%P\n» , and then pass that to the tar command (it takes filenames from STDIN using -T — ). The -C option is needed so tar knows where the files with relative names are located. The —no-recursion flag is so that tar doesn’t recurse into folders it is told to archive (causing duplicate files).
If you need to do something special with filenames (filtering, following symlinks etc), the find command is pretty powerful, and you can test it by just removing the tar part of the above command:
$ find /my/dir/ -printf "%P\n" -type f -o -type l -o -type d > textfile.txt > documentation.pdf > subfolder2 > subfolder > subfolder/.gitignore For example if you want to filter PDF files, add ! -name ‘*.pdf’
$ find /my/dir/ -printf "%P\n" -type f ! -name '*.pdf' -o -type l -o -type d > textfile.txt > subfolder2 > subfolder > subfolder/.gitignore Non-GNU find
The command uses printf (available in GNU find ) which tells find to print its results with relative paths. However, if you don’t have GNU find , this works to make the paths relative (removes parents with sed ):
find /my/dir/ -type f -o -type l -o -type d | sed s,^/my/dir/,, | tar -czf mydir.tgz --no-recursion -C /my/dir/ -T - @SandRock I agree it’s strange that achieving something so basic as this is so tricky with tar. Probably just historical reasons.
Have a look at —transform / —xform , it gives you the opportunity to massage the file name as the file is added to the archive:
% mkdir my_directory % touch my_directory/file1 % touch my_directory/file2 % touch my_directory/.hiddenfile1 % touch my_directory/.hiddenfile2 % tar -v -c -f my_dir.tgz --xform='s,my_directory/,,' $(find my_directory -type f) my_directory/file2 my_directory/.hiddenfile1 my_directory/.hiddenfile2 my_directory/file1 % tar -t -f my_dir.tgz file2 .hiddenfile1 .hiddenfile2 file1 Transform expression is similar to that of sed , and we can use separators other than / ( , in the above example).
https://www.gnu.org/software/tar/manual/html_section/tar_52.html
Good solution, but it might cause file list too long . My solution prevents that and is more flexible as well.
cd my_directory tar zcvf ../my_directory.tar.gz * This Answer should work in most situations. Notice however how the filenames are stored in the tar file as, for example, ./file1 rather than just file1 . I found that this caused problems when using this method to manipulate tarballs used as package files in BuildRoot.
One solution is to use some Bash globs to list all files except for .. like this:
tar -C my_dir -zcvf my_dir.tar.gz .[^.]* . * * This is a trick I learnt from this answer.
Now tar will return an error if there are no files matching . * or .[^.]* , but it will still work. If the error is a problem (you are checking for success in a script), this works:
shopt -s nullglob tar -C my_dir -zcvf my_dir.tar.gz .[^.]* . * * shopt -u nullglob Though now we are messing with shell options, we might decide that it is neater to have * match hidden files:
shopt -s dotglob tar -C my_dir -zcvf my_dir.tar.gz * shopt -u dotglob This might not work where your shell globs * in the current directory, so alternatively, use:
shopt -s dotglob cd my_dir tar -zcvf ../my_dir.tar.gz * cd .. shopt -u dotglob I get wierd errors when I do this tar: start.sh: Cannot stat: No such file or directory This happens to all files in my current directory! How do I avoid this?
This does not work — at least in some shells (e.g., bash, version 5.0.17, Ubuntu 20.04) — because the * glob is evaluated by the shell before tar takes over and changes directory ( -C my_dir ). So, it tries to archive the files in the current dir where the tar command is executed, instead of the changed-dir, my_dir . You may get lucky, if the file names in the current dir just happen to match the names in the changed-dir, my_dir , but that’s not generally reliable. 🙂 . Most likely, this is the reason for the errors above.
@Trevor I think this is what the 4th example works around (cd to the directory first, then run tar without the -C option)
cd my_directory && tar -czvf ../my_directory.tar.gz $(ls -A) && cd .. This one worked for me and it’s include all hidden files without putting all files in a root directory named «.» like in tomoe’s answer :
cd DIRECTORY tar -czf NAME.tar.gz * the asterisk will include everything even hidden ones
Command
to create a standard archive file.
find my_directory/ -maxdepth 1 -printf «%P\n» | tar -cvf my_archive.tar -C my_directory/ -T —
Packed files and dirs are in the root of the archive without path info and deeper files have relative path.
There are no weird looking ‘./’ in front of files and dirs. (‘./file’)
No special files ‘.’ are included.
It seems that another tool, like find or ls ( ls -A -1 ) is needed to accomplish these goals and tar using just its arguments is unable to pick files and create an archive with such requirements.
Using above command creates an archive tar file which can be further processed or delivered to someone without looking weird or needing an explanation or a tool to unpack.
Arguments description
-maxdepth 1
Descend at most 1 level — No recursing.
-printf
print format on the standard output
%P File’s name with the name of the starting-point under which it was found removed.
\n Newline
printf does not add a newline at the end of the string. It must be added here
tar:
-C DIR , —directory=DIR
change to directory DIR
-T FILE , —files-from=FILE
get names to extract or create from FILE
—
that FILE from above is the standard input, from the pipe
Comments on other solutions.
The same result might be achieved using solution described by @aross.
The difference with the solution here is in that which tool is doing the recursing. If you leave the job to find , every filepath name, goes through the pipe. It also sends all directory names, which tar with —no-recursion ignores or adds as empty ones followed by all files in each directory. If there was unexpected output as errors in file read from find , tar would not know or care what’s going on.
But with further checks, like processing error stream from find, it might be a good solution where many options and filters on files are required.
I prefer to leave the recursing on tar, it does seem simpler and as such more stable solution.
With my complicated directory structure, I feel more confident the archive is complete when tar will not report an error.
Another solution using find proposed by @serendrewpity seems to be fine, but it fails on filenames with spaces. Difference is that output from find supplied by $() sub-shell is space-divided. It might be possible to add quotes using printf, but it would further complicate the statement.
There is no reason to cd into the my_directory and then back, while using ../my_archive.tar for tar path, because TAR has -C DIR , —directory=DIR command which is there just for this purpose.
Using . (dot) will include dots
Using * will let shell supply the input file list. It might be possible using shell options to include dot files. But it’s complicated. The command must be executed in shell which allows that. Enabling and disabling must be done before and after tar command. And it will fail if root dir of future archive contains too many files.
That last point also applies to all those solutions which are not using pipe.
Most of solutions are creating a dir inside which are the files and dirs. That is barely ever desired.