mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1518] [RequestPerform] hangs with successful response on docker/alpine #797
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#797
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aamorozov on GitHub (Jan 14, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1518
Additional Information
The issue occurs with my setup on multiple versions of s3fs.
I tried using the password file option instead with the following command:
,but the credentials generated from converting with
assume-role-with-web-identitydid not seem to work with s3fs with the following error:I then switched to using the
iam_roleoption, and it does seem to work but hangs midway and the entrypoint script never finishes executing.Version of s3fs being used (s3fs --version)
Tested with
1.88,1.87and1.86.Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.9-r1
GNU/Linux Distribution, if applicable (cat /etc/os-release)
Docker image:
node:14.14.0-alpine3.12Packages installed to support s3fs in alpine
s3fs command line used, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
@aamorozov commented on GitHub (Jan 15, 2021):
For context, this runs in a docker container within k8s.
The service has a service role with permissions to access that bucket assigned to it.
I'm converting the
AWS_ROLE_ARNto regular credentials,AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEYand writing them to.passwd-s3fs, which I use as an option arg tos3fsscript.It gives me a 403 error if used with the
passwd_fileoption, and hangs if I use it with the role@aamorozov commented on GitHub (Jan 15, 2021):
Update:
I've tried with the approach described here https://github.com/s3fs-fuse/s3fs-fuse/pull/1008#issuecomment-483724082 using s3fs friendly aws credentials, but it still hangs midway. The credentials are valid and do work with aws s3 cli's commands.