I thought tar archive.tar /users/mylocation
would work, but it doesn't. How can I do that?
5 Answers
To extract an archive to a directory different from the current, use the -C
, or --directory
, tar option, as in
tar -xf archive.tar -C /target/directory
Note that the target directory has to exist before running that command (it can be created by mkdir /target/directory
).
Read the manual page (command: man tar
) for other options.
-
3If it's a larger file, when you run the command, all you get is no output for several seconds or even minutes while it's working. You can fix this by adding the
-v
flag (verbose mode) which lists the name of each file as it extracts it. Commented May 7, 2015 at 6:15 -
1If you're having troubles with this, note the
--strip-components=1
advice from the other answer as well. Commented Dec 25, 2015 at 19:17 -
27
-
50Isn't it amazing that, after all these years, with all the options
tar
has accumulated, there still isn't an option to create the output directory if it doesn't exist?– EM0Commented Apr 13, 2018 at 8:21 -
2I totally agree, there should be an option to create the output directory if it doesn't exist. Otherwise, you can just extract the file and use
mv
.– mathleteCommented May 13, 2019 at 11:50
Note that if your tarball already contains a directory name you want to change, add the --strip-components=1
option:
tar xf archive.tar -C /target/directory --strip-components=1
-
3Thank you. Downloads via wget/etc always have a 'parent' directory. This is the complete answer imo - or should be noted in answer above.– B. SheaCommented Apr 28, 2017 at 16:51
-
3Just what I was looking for.
--strip-components
is so useful when running provisioners that might use different versions. This way/target/directory
can be a generic name, without having to worry about how the provider chose to name their archive folder.– Jack_HuCommented Jan 30, 2019 at 17:54 -
1Just a heads up, this can remove any number of leading directories, not just one: --strip-components=NUMBER strip NUMBER leading components from file names on extraction– ᴍᴇʜᴏᴠCommented Oct 28, 2019 at 7:37
Combining the previous answers and comments:
To simply extract the contents and create target directory if it is missing:
mkdir -p /target/directory && tar xf archive.tar -C /target/directory
To extract and also remove the root(first level) directory in the zip
mkdir -p /target/directory && tar xf archive.tar -C /target/directory --strip-components=1
Another option is to use --one-top-level. This will automatically create a directory based on the filename of the original.
tar zxvf filename.tgz --one-top-level
Additionally if you want, you can specify your own and tar will create it automatically.
tar zxvf filename.tgz --one-top-level=new_directory
-
6I'm using GNU tar 1.26 and I get an unrecognized option error for
--one-top-level
Commented Sep 24, 2018 at 14:29 -
2This is the answer I needed. Very useful "not" to have to specify the directory name, or remember special code that will refer back to the file for the name. Thank you. Commented Jul 20, 2019 at 0:51
-
2For anyone on macOS, you'll need to install
gnu-tar
withbrew install gnu-tar
and then usegtar
to get this command line option.– gsgxCommented Sep 30, 2022 at 4:47
What I found interesting in relation to extraction is, that it depends how you created the archive, see this example
cd /tmp
mkdir folder
touch folder/file.txt
when you do tar -zcvf folder.tar.gz folder
everything is as expected = when you untar it now it will be untarred (folder will be create, if you removed it) as /tmp/folder/
.
But, when you will create tar as tar -zcvf tmp-folder.tar.gz /tmp/folder
and you untar it in /tmp
folder, the result will be /tmp/tmp/folder
directory ! In such case you have to untar it to /
- tar -xf tmp-folder.tar.gz -C /
-C, --directory DIR\n change to directory DIR
should rather be described aschange output directory to DIR (will fail if DIR doesn't exist)
. Thanks @Mich. See also @Bryan_Larsen's answer.tar xfC archive.tar mydir
ortar -C mydir -xf archive.tar
. It's only mixing traditional-style and GNU-style flags that breaks things, as... is honestly kind of expected. Traditional flags are passed all as one blob as the first argument. You can't expect them to work if they're not the first. (I mean, yes, it's possible to interpret it anyway -- my point is that'd be above and beyond, not standard)