Using the no-seek argument causes a bug
Opened this issue · 0 comments
HidemaruOwO commented
- Plugin version (or commit ref) : latest
- Docker version : 24.0.6, build ed223bc
- Plugin type : legacy
- Operating system: Fedora 38
Description
If I create a volume using the --no-seek
option as args, the files in the volume will be empty (do not get)
SEEK should be avoided due to its high processing load
...
Logs
- Don't use
--no-seek
In this case, the existence of the file is firmly confirmed.
root@thinkcentre-any ~# docker volume rm nextcloud_dav && docker volume create --driver sapk/plugin-rclone --opt config="$(base64 ~/.config/rclone/rclone.conf)" --opt remote=nextcloud: --name nextcloud_dav --opt args="--allow-root --allow-other"
nextcloud_dav
nextcloud_dav
root@thinkcentre-any ~# docker run -itd --name testvolume -v nextcloud_dav:/nc_dav busybox && docker exec -it testvolume /bin/sh && docker stop testvolume && docker rm testvolume
6a36381e1127a4876653e6df99d86fc5f85c0baef14bd72ee8169b9835ef7bb1
/ # ls nc_dav
Audio Books Documents Photos Video public
/ #
- Use
--no-seek
In this case, the existence of the file cannot be firmly confirmed.
root@thinkcentre-any ~# docker volume rm nextcloud_dav && docker volume create --driver sapk/plugin-rclone --opt config="$(base64 ~/.config/rclone/rclone.conf)" --opt remote=nextcloud: --name nextcloud_dav --opt args="--allow-root --allow-other --no-seek"
nextcloud_dav
nextcloud_dav
root@thinkcentre-any ~# docker run -itd --name testvolume -v nextcloud_dav:/nc_dav busybox && docker exec -it testvolume /bin/sh && docker stop testvolume && docker rm testvolume
b7f961e9f8290f9faedbfd07adcb8f39a70018a6d1ccd855c3ca460ac7586532
/ # ls nc_dav/
/ #