1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
To resolve the first issue and mount your S3 bucket to a non-empty directory, you should modify your mount command to include the nonempty option.
For the second issue, ensure that the path you are trying to mount to actually exists on your filesystem. If the path is correct, review your mount command for any typos or configuration errors.
Contenus pertinents
- demandé il y a 4 mois
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a 2 mois
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
I don't see that the mount-s3 service has that option:
Usage: mount-s3 <BUCKET_NAME|DIRECTORY|--prefix <PREFIX>|--region <REGION>|--endpoint-url <ENDPOINT_URL>|--force-path-style|--transfer-acceleration|--dual-stack|--requester-pays|--bucket-type <BUCKET_TYPE>|--no-sign-request|--profile <PROFILE>|--read-only|--storage-class <STORAGE_CLASS>|--allow-delete|--allow-overwrite|--auto-unmount|--allow-root|--allow-other|--maximum-throughput-gbps <N>|--max-threads <N>|--part-size <PART_SIZE>|--uid <UID>|--gid<GID>|--dir-mode <DIR_MODE>|--file-mode <FILE_MODE>|--foreground|--expected-bucket-owner <AWS_ACCOUNT_ID>|--log-directory <DIRECTORY>|--log-metrics|--debug|--debug-crt|--no-log|--cache <DIRECTORY>|--metadata-ttl <SECONDS>|--max-cache-size <MiB>|--user-agent-prefix <PREFIX>>
you might consider alternative methods or tools for mounting S3 buckets, such as s3fs-fuse, which supports the nonempty option. With s3fs-fuse, you can typically add the nonempty option to the mount command like so:
Make sure to replace yourbucketname with your actual S3 bucket name and /path/to/mountpoint with your desired mount point.