fs-fuse | Export any Node.js fs -like object as a FUSE filesystem | File Utils library

A workaround is:

• start unionfs with option auto_unmount
• instead of fusermount -u, kill the last unionfs process with pkill -nf ${ROOT_DIR}
  (kills the most recent process that has ${ROOT_DIR} in its arguments)

The resulting script:

Does it work if you specify the IAM role explicitly?

It looks like there may be an issue with retrieval of the IAM role information (needed with iam_role=auto) when tokens are required.

Additionally, when testing this, I had issues with when the -f option is used, so also try removing that.

Below are logs that show the proper token retrieval when mounting a bucket with the following command. Bucket access via the mount point works as expected.

$ sudo s3fs /mnt -o iam_role=s3fs-testing,allow_other,uid=1000,gid=1000,mp_umask=007,use_cache=/tmp/s3foldercache,dbglevel=debug

My solution, thanks to Charles Duffy hints.

1. I created a sh file (start.sh) that contains:

You use the IRSA system, attaching an IAM role to a Kubernetes service account and then attaching that K8s SA to your pod. See https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html for a starting point.

You could use elastic file system which is supported by EKS:

Applications running in Kubernetes can use EFS file systems to share data between pods in a scale-out group, or with other applications running within or outside of Kubernetes. EFS can also help Kubernetes applications be highly available because all data written to EFS is written to multiple AWS Availability zones. If a Kubernetes pod is terminated and relaunched, the CSI driver will reconnect the EFS file system, even if the pod is relaunched in a different AWS Availability Zone.

But its not S3 and it does not have versioning of files such as S3 has. You would have to add such functionality yourself, e.g. by keeping everything in a git repository on the EFS file system.

s3fs master branch requires a newer kernel and glibc:

https://github.com/s3fs-fuse/s3fs-fuse/issues/1354

You can work around this by compiling s3fs 1.86 instead.

The fftw recipe is set up to create a few different packages (RPM) like libfftw, libfftwl, libfftwf, fftw-wisdom, fftwl-wisdom, fftwf-wisdom, and fftw-wisdom-to-conf. You probably want to add one or more of those. It seems there is no actual fftw package.

It is important to remember that IMAGE_INSTALL and RDEPEND lists items from the package namespace, while DEPENDS lists items from the recipe namespace.

If you are unsure about which package you want to install you can inspect the packages-split folder for fftw in tmp/work to see which files are included in which package.

You can install the mime types via: yum install mailcap.

If you want to set up many containers at one time you need to configure docker-compose file and that's all. You needn't build the container from the image manually. It docker-compose does when first time builds and runs containers.

Create an empty folder called 'docker' and inside 'docker' directory create a directory with the name 's3', put there your docker file there. Move there and there in terminal type: