

- Cannot utime operation not permitted archive#
- Cannot utime operation not permitted code#
- Cannot utime operation not permitted windows#
I’m so confused how docker manage the permissions in volumes. So, my question is, how can I restore my volume without this permission issues? I already try to restore the volume using user and group tags (root) in docker command and in the untar command, but no sucess. I’m almost sure this problem is related to permission issues in the process of untar the volume. sudo docker run -rm -volume MY_VOLUME:/data -volume $(pwd):/backup ubuntu tar xvf /backup/MY_VOLUME.tar -C /data -p -strip 1
.jpg)
Cannot utime operation not permitted code#
When I try to restore my volume with the command below, I’m getting the error message: “Cannot utime: Operation not permitted”. Basically it untars a file a deploys the code to the relevent directories. I sended this file to other machine that runs a linux based system. docker run -rm -volume MY_VOLUME:/data -volume %cd%:/backup ubuntu tar cvf /backup/MY_VOLUME.tar /data Fedora 25 tar errors from backup script er: Cannot time Operation not permitted Ask Question. When I inspect the file using 7-zip, I can see that the files have no user assigned and root group assigned to them. I have made a backup to a tar file using the command below and all seeing to work.
Cannot utime operation not permitted windows#
By default, the files are owned by root and not readable by somebody else.I have a docker volume created in a windows system. ll /usr/share/rvm total 124K drwxrwsr-x 2 root rvm 4.0K May 10 13:03 archives drwxrwsr-x 2 root rvm 4.0K May 10 12:59 bin drwxrwsr-x 3 root rvm 4. Set the file permission on the filesystem.

In that case there is a possibility to use proper mount options. So either copy as root or change the permissions on target so that you have a write permission on media directory.Īs pointed out it's not possible to change permissions nor ownership on mounted NTFS filesystem. It seems to me that permissions are not correctly set.īut you can't create a file in a destination because the directory media is not writeable by you, only root can do that chowning the folder to the current user makes tar fail silently so the installer can continue. Judging from the OP's own answer, it seems then that the installer checks tar's exit code and stops if an error was encountered. Permissions are restored for both the folder and the files, and no error is thrown even though user2 ownership could not be restored.

Here's what happens if the extraction is performed in a directory owned by user1 instead: $ tar xpvzf The files are however extracted, although owned by user1. Tar throws an error because it cannot change ownership and permissions for files owned by user2. Tar: Exiting with failure status due to previous errors : Cannot change mode to rwxrwxr-x: Operation not permitted
Cannot utime operation not permitted archive#
If we extract the archive in a directory owned by user2 with permissions 777, here's the outcome: $ tar xpvzf Let's say we are user1 and have created an archive with tar cvpzf. Update: Here's some more details about tar's behaviour.
Reference: read this informative Q&A on askubuntu:Įven if you use tar's -same-owner flag, you will still need to extract the files as root to preserve ownership. Error 1 (0x00000001) (Not owner) in execution of system call utime with parameter (/sapmnt/Question: Permissions cannot be restored for a tar
