You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After executing this command and accessing the container, I can see the S3 files available in /opt/s3fs/bucket. However, they are not mounted in the host machine's path /mnt/tmp. A similar issue occurs when using Docker Compose.
The text was updated successfully, but these errors were encountered:
I ran the following Docker command:
docker run -d
--device /dev/fuse
--cap-add SYS_ADMIN
--security-opt apparmor=unconfined
-e AWS_S3_BUCKET=s3input
-e AWS_S3_ACCESS_KEY_ID=
-e AWS_S3_SECRET_ACCESS_KEY=
-e UID=$(id -u)
-e GID=$(id -g)
-v /mnt/tmp:/opt/s3fs/bucket:rshared
efrecon/s3fs:1.90
After executing this command and accessing the container, I can see the S3 files available in /opt/s3fs/bucket. However, they are not mounted in the host machine's path /mnt/tmp. A similar issue occurs when using Docker Compose.
The text was updated successfully, but these errors were encountered: