[GH-ISSUE #400] Using s3fs behind a proxy #212

Closed
opened 2026-03-04 01:43:17 +03:00 by kerem · 5 comments
Owner

Originally created by @gnwlyonme on GitHub (Apr 20, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/400

s3fs does not use http_proxy, all_proxy, etc... env vars when used behind a proxy.

I had to add the following in curl.cpp in function S3fsCurl::ResetHandle in order to mount S3
curl_easy_setopt(hCurl, CURLOPT_PROXY, "http://corp-proxy:8080");

Is this the only option currently, or is there a way it can be set? If not, an -o proxy option would be a nice feature to have.

Thanks,
Mike

Originally created by @gnwlyonme on GitHub (Apr 20, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/400 s3fs does not use http_proxy, all_proxy, etc... env vars when used behind a proxy. I had to add the following in curl.cpp in function S3fsCurl::ResetHandle in order to mount S3 curl_easy_setopt(hCurl, CURLOPT_PROXY, "http://corp-proxy:8080"); Is this the only option currently, or is there a way it can be set? If not, an -o proxy option would be a nice feature to have. Thanks, Mike
kerem 2026-03-04 01:43:17 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@gaul commented on GitHub (Apr 20, 2016):

@gnwlyonme Run export http_proxy=127.0.0.1:1080 before invoking s3fs.

<!-- gh-comment-id:212526864 --> @gaul commented on GitHub (Apr 20, 2016): @gnwlyonme Run `export http_proxy=127.0.0.1:1080` before invoking `s3fs`.
Author
Owner

@yren commented on GitHub (May 10, 2016):

I use s3fs in a docker container and behind a proxy,
I tried this
Run export http_proxy=127.0.0.1:1080 , then invoking s3fs . But it's not work.
The error message "fuse: failed to exec fusermount: No such file or directory"

Any suggestion on this. Thanks.
BTW, this can work on docker host machine.

<!-- gh-comment-id:218096869 --> @yren commented on GitHub (May 10, 2016): I use s3fs in a docker container and behind a proxy, I tried this Run export http_proxy=127.0.0.1:1080 , then invoking s3fs . But it's not work. The error message "fuse: failed to exec fusermount: No such file or directory" Any suggestion on this. Thanks. BTW, this can work on docker host machine.
Author
Owner

@gnwlyonme commented on GitHub (May 10, 2016):

yren,
Have you tried adding --privileged to docker run?
That fixed my problem.

<!-- gh-comment-id:218147215 --> @gnwlyonme commented on GitHub (May 10, 2016): yren, Have you tried adding --privileged to docker run? That fixed my problem.
Author
Owner

@yren commented on GitHub (May 11, 2016):

Cool, it works for me. Thanks @gnwlyonme

<!-- gh-comment-id:218344328 --> @yren commented on GitHub (May 11, 2016): Cool, it works for me. Thanks @gnwlyonme
Author
Owner

@ggtakec commented on GitHub (May 14, 2016):

@andrewgaul thank you.
@gnwlyonme and @yren I'm sorry for my late reply.

So the issue has been resolved, I closed this issue.
If there is a problem to continue, please reopen this issue or post new issue.

Thanks all.

<!-- gh-comment-id:219214072 --> @ggtakec commented on GitHub (May 14, 2016): @andrewgaul thank you. @gnwlyonme and @yren I'm sorry for my late reply. So the issue has been resolved, I closed this issue. If there is a problem to continue, please reopen this issue or post new issue. Thanks all.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#212
No description provided.