[{"_1":2,"_176":-5,"_177":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_155":156},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":17},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_108":109,"_146":-5,"_147":11,"_148":17,"_149":11,"_150":-5,"_151":11,"_152":-5,"_153":154},"canonicalUrl","https://hub.docker.com/r/nebtex/s3fs/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","nebtex","reponame","s3fs","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2016-09-10T16:27:52.464621Z","description","docker-s3fs","is_private","last_updated","2016-09-10T16:31:39.819341Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",168,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","docker-s3fs\n===========\n\n**[S3fs][s3fs]** docker build for version 1.80. \n\n- [Docker engine after 1.10](#docker-egnine-after-1.10)\n- [Docker engine before 1.10](#docker-engine-before-1.10)\n\n### Docker engine after 1.10\n\nDocker engine 1.10 added a new feature which allows containers to share the host mount namespace. This feature makes it possible to mount a s3fs container file system to a host file system through a shared mount, providing a persistent network storage with S3 backend. \n\n**Prerequsites**\n\n* Docker engine 1.10.x\n* If the docker service is managed by systemd, you need to remove __MountFlags=slave__. See [issue](https://github.com/docker/docker/pull/22806). Example to fix this on CoreOS:\n\n\t\t# cp /usr/lib/systemd/system/docker.service /etc/systemd/system/\n\t\t# sed -i 's/MountFlags=slave/#MountFlags=slave/' /etc/systemd/system/docker.service\n\t\t# systemctl daemon-reload\n\t\t# systemctl restart docker.service\n\t\t\n* Make a shared mountpoint on host\n\n\t\t# mkdir /mnt/mydata\n\t\t# mount --bind /mnt/mydata /mnt/mydata\n\t\t# mount --make-shared /mnt/mydata\n\t\t# findmnt -o TARGET,PROPAGATION /mnt/mydata\n\t\tTARGET PROPAGATION\n\t\t/mnt/mydata\t\t shared\n\t\t\n* Create AWS credential file (or use role-based crentials)\n\n\t\t# echo \":\" > /root/.s3fs\n\t\t# chmod 400 /root/.s3fs\n\n**Run the S3fs container**\n\n**As a systemd service**\n\nCreate a systemd unit /etc/systemd/system/s3fs.service with the following content:\n\n\t[Unit]\n\tDescription=S3fs Service\n\n\t[Service]\n\tExecStartPre=-/usr/bin/docker kill %n\n\tExecStartPre=-/usr/bin/docker rm %n\n\tExecStart=/usr/bin/docker run --rm --name %n -v /root/.s3fs:/root/.s3fs --security-opt apparmor:unconfined --cap-add mknod --cap-add sys_admin --device=/dev/fuse -v /mnt/mydata:/m\n\tnt/mydata:shared xueshanf/s3fs /usr/bin/s3fs -f -o allow_other -o use_cache=/tmp -o passwd_file=/root/.s3fs /mnt/mydata\n\tTimeoutStartSec=5min\n\tExecStop=-/usr/bin/docker stop %n\n\tRestartSec=5\n\tRestart=always\n\t\nIt is important to use the **-f** flag to keep the s3fs container running in foreground. \n\nStart the unit:\n\n\t# systemctl start s3fs.service\n\t\nNow you should be able to see file system under /mnt/mydata on host. Changes you make there will be reflected on the S3 bucket, and shared by other hosts using the system s3fs.service unit. \n\nNote that, if you previously created the files in the S3 bucket with other tools such as s3cmd, awscli, the s3fs file system won't be able to get file ownership and mode correctly. You will see directories listed with permissions like \"d------\". To fix this, you can correct the permissions under /mnt/mydata on host. s3fs will re-upload s3fs specific z-amz-metadata-* headers. \n\n**With docker-compose**\n\nGet [docker-compose](https://docs.docker.com/compose/install/)\n\nCreate a shared mount on the host as described above.\n\nYou can use the `docker-compose.yml` for starting the s3fs container with a simple command\n\n\tdocker-compose up -d\n\nYou have to edit it first and set `AWSACCESSKEYID` and `AWSSECRETACCESSKEY` and replace `S3_BUCKET_NAME` with the name of your S3 bucket.\n\nFor mounting the S3 folder into other containers, you have to define the host mount path as a volume. `volumes-from` does _not_ work with a FUSE-based mount.\nSo this way the s3fs container mounts the S3 bucket to a folder on the host which is then mapped into other containers.\n\n### Docker engine before 1.10\n\nBefore Docker version 1.10, s3fs mounted volumes (FUSE-based file system) in the container are not visiable from docker host through -v `:` option, nor from other containsers through --volumes-from `. However, you can still copy data out and make it available on the docker hosts and other containers. \n\nThe following examples show how to start s3fs container with EC2 IAM role-based credential or with an IAM user that has permission to access your AWS s3 bucket. \n\nNote: You should not include _s3://_ in the bucket name, otherwise, you get _Transport endpoint is not connected error_.\n\n* Run the image with IAM role-based credential\n\n docker pull xueshanf/s3fs\n docker run --rm --name s3fs-container --cap-add mknod --cap-add sys_admin --device=/dev/fuse xueshanf/s3fs /usr/bin/s3fs -o allow_other -o use_cache=/tmp -o iam_role= /mnt/mydata\n \n* Run the image as an IAM user \n\n\t\t$ cat accessId:acessSecrect > /root/.s3fs\n\t\t$ chmod 400 /root/.s3fs\n\t\t$ docker run -v /root/.s3fs:/root/.s3fs --name s3fs-container --rm --cap-add mknod --cap-add sys_admin --device=/dev/fuse xueshanf/s3fs /usr/bin/s3fs -o allow_other -o use_cache=/tmp -o passwd_file=/root/.s3fs /mnt/mydata\n\t\t\nKeep the container running in the above foreground window, start another terminal to run the following example operations. \n\n * List file system and copy a file\n\n \t\t$ docker exec s3fs-container ls /mnt/mydata\n \t\t$ docker exec s3fs-container cat /mnt/mydata/file1 > /tmp/file1\n \t\t\n* Mount an entire bucket and copy files to a bind-mount volume _/opt/data_ on host:\n\n $ docker run --rm --cap-add mknod --cap-add sys_admin --device=/dev/fuse -v /root/.s3fs:/root/.s3fs -v /opt/data:/data -it xueshanf/s3fs\n root@88c090451cce:/# /usr/bin/s3fs -o allow_other -o use_cache=/tmp -o iam_role=controller mybucket /mnt/mydata\n cp -r /mnt/mydata /data\n umount /mnt/mydata\n exit\n \n* Debugging mount problems\n\n /usr/bin/s3fs -f -d -o allow_other -o use_cache=/tmp -o iam_role= \n\nNote\n----\n\n You need to add extra sys-capabilities to use fuse:\n\n --cap-add mknod --cap-add sys_admin --device=/dev/fuse\n\n You can always run it with `--privileged`. However this should be avoided if possible. Run with the more restricted set above.\n\n See [Issue 6616](https://github.com/docker/docker/issues/6616).\n\n[s3fs]: https://github.com/s3fs-fuse/s3fs-fuse\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",160192030,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_103":104,"_105":98,"_106":98,"_107":17},"id","598fed4272084667983e2dd9e5eca87d","uuid","598fed42-7208-4667-983e-2dd9e5eca87d","type","organization","orgname","full_name","Nebular Vortex","location","Bogota","company","","profile_url","https://www.nebtex.com","date_joined","2015-03-02T09:43:54.667834Z","gravatar_url","https://www.gravatar.com/avatar/e91673f08e7e10c8d0e9331baecd5334?s=80&r=g&d=mm","gravatar_email","badge","is_active","recentTags",[110],{"_111":40,"_112":113,"_114":115,"_86":116,"_117":118,"_46":135,"_136":113,"_137":29,"_138":52,"_53":139,"_140":141,"_142":126,"_143":135,"_144":62,"_145":17},"content_type","creator",233103,"full_size",160184284,4778955,"images",[119],{"_120":121,"_122":123,"_124":98,"_125":126,"_127":128,"_129":130,"_131":98,"_132":-5,"_133":115,"_59":62,"_134":-5},"architecture","amd64","digest","sha256:399d40aee8d03945a6cbb9730a5932290f1bc8b05a2603d1f2c5c3ee3d9655a2","features","last_pulled","2026-09-19T21:59:50.323850783Z","last_pushed","2016-09-10T16:31:40Z","os","linux","os_features","os_version","size","variant","2016-09-10T16:31:39.328885Z","last_updater","last_updater_username","media_type","1.8","repository",908675,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":157,"_164":165,"_153":174,"_175":11},{"_36":158,"_38":159,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":160,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":161,"_75":17,"_76":163,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":162},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_166":60,"_167":-5,"_168":-5,"_169":170},"count","next","previous","results",[171],{"_111":40,"_112":113,"_114":115,"_86":116,"_117":172,"_46":135,"_136":113,"_137":29,"_138":52,"_53":139,"_140":141,"_142":126,"_143":135,"_144":62,"_145":17},[173],{"_120":121,"_122":123,"_124":98,"_125":126,"_127":128,"_129":130,"_131":98,"_132":-5,"_133":115,"_59":62,"_134":-5},[],"canDeleteTags","actionData","errors"]

nebtex/s3fs

Tags for nebtex/s3fs