mjhjmtu

So I first testing a simpler scenario I was able to correctly use the tar --exclude option, in the simple scenario, a folder, "pack" contains two files:

1. text.txt


2. mongod.lock

Screenshot of pack folder:

Running the command:

tar --exclude='mongod.lock' -cvf foo.tar -C /home/bogden/repos/devops/scripts/pack .

This correctly ignored a file named "mongod.lock" in the "pack" folder, created a tar named "foo.tar", that contained one file, tar verbose output:

The unpacking of the tar archive proves "mongod.lock" was ignored:

Now in my scenario I am archiving a docker container volume, and trying to exclude this "mongod.lock". The fact that this is a docker container volume does not matter that much except perhaps some kind of file path I need to include in my --exclude= pattern.

docker run --rm --volumes-from example.db.container -v /backup/volumes:/backup centos7 tar --exclude='mongod.lock' -cvf /backup/backup.tar -C /data/db .

the mongod.lock is archived as well, it is not excluded:

I have also tried --exclude= patterns:

• ./mongod.lock


• /mongod.lock


• **.lock


• /data/db/mongod.lock

I am guessing I have some folder path that I need to include in my ignore pattern but I am not sure