Docker-sync: Error on syncing symlinks with rsync? error code 95

[trungtnm]

I got this error when run docker-sync-stack start using rsync, on many files :
rsync: failed to set permissions on "front/bin/phpmd" (in volume): Not supported (95)
rsync: failed to set permissions on "admin/bin/phpunit" (in volume): Not supported (95)

After investigating, i found that this happened when the files caused the error are symlinks. If i exclude these files from syncing or remove the symlinks, everything works fine.

[EugenMayer]

Are you syncing your node_modules?

[trungtnm]

@EugenMayer : no, i use nearly default configuration as here and do not have node_modules in my projects. It happens with some files generated by PHP Composer (see link below)
files with symlinks

[EugenMayer]

please check if those binaries are compiled binaries, if yes, they might be symlinks on your OSX to a different location and if synced, they do not accists.

"Not supported" is most probably an issue that the symlink is simply broken on the container, please also see the issue queue for issues like https://github.com/EugenMayer/docker-sync/issues/143

[anthwinter]

you could try including -L within the sync_args options of the docker-sync.yml

From the rsync docs: "When symlinks are encountered, the item that they point to (the referent) is copied, rather than the symlink."

There are also other options to attempt if you check -l, -L, -k and -K on this page: https://linux.die.net/man/1/rsync

[trungtnm]

thanks @anthwinter , it works well with -L arg.

[kallehauge]

@trungtnm have you tried to delete a file and see if it gets removed in the container? Because that is not the case for me :)

[trungtnm]

@kallehauge yes, this is the issue with symlinks :). I think you can try with --delete arg.

[kallehauge]

That's brilliant @trungtnm - I didn't even think of that :smile:

[EugenMayer]

Yes delete is not used with rsync intentionally, because there are too many edge cases. If you want to use delete, you should thing about using unison not rsync as a strategy.

[EugenMayer]

Is this issue still open actually, or did you solve it by now?

[trungtnm]

Yes, it resolved! I will close this.