Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation Fault with curl call and instagram #5846

Closed
3 tasks done
florentbolo opened this issue Jul 15, 2021 · 5 comments
Closed
3 tasks done

Segmentation Fault with curl call and instagram #5846

florentbolo opened this issue Jul 15, 2021 · 5 comments

Comments

@florentbolo
Copy link

Continuation of : docker-library/php#1176 (comment)

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: E49637BF-924B-41E1-B645-976E1B840FCF/20210715203530

Expected behavior

Hi !
I want to
curl https://graph.instagram.com
from my container

Actual behavior

return
segment fault
but it worked with any other websites
And curl instagram in my local terminal worked too

It might be after the installation of Openvpn via Tunnelbclick or maybe not.

  • macOS Version: Mac Os Big Sur
  • Intel chip or Apple chip: M1
  • Docker Desktop Version: 3.5.2

Thanks for your suggestions :)

@thaJeztah
Copy link
Member

/cc @chris-crone @tonistiigi ISTR you had seen this as well, and looked into this

@chris-crone
Copy link
Member

chris-crone commented Jul 16, 2021

@thaJeztah this looks similar yes.

@florentbolo are you using a Debian Buster based image? If so, I believe you've run into an issue with libcrypto that @djs55 has reported upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989604

There are a couple of workarounds that you can use:

  1. Use another image, e.g.: alpine based, older or newer Debian based
  2. Tell curl to use different ciphers: curl --tls-max 1.2 https://graph.instagram.com

For (2), you might also need to specify a cipher using --ciphers based on what the server supports

@florentbolo
Copy link
Author

@chris-crone Thanks for your answer.
curl --tls-max 1.2 https://graph.instagram.com

Worked for me !

@docker-robott
Copy link
Collaborator

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Feb 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants