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

Cleanup build #26

Open
dimaqq opened this issue Mar 23, 2020 · 2 comments
Open

Cleanup build #26

dimaqq opened this issue Mar 23, 2020 · 2 comments

Comments

@dimaqq
Copy link
Owner

dimaqq commented Mar 23, 2020

What's required to build awaitwhat in a python:alpine container:

  • apk update
  • apk upgrade (dunno)
  • apk add build-base (to get gcc)
  • apk add libffi-dev (I guess I get it?)
  • apk add openssl-dev (why?)
@pyjavo
Copy link
Collaborator

pyjavo commented Mar 23, 2020

Hi there!
I haven't try tu build it yet but I think you should check this

https://pythonspeed.com/articles/base-image-python-docker-images/

Recently I was working on a project with alpine and we had to switch to another distribution (debian buster) because it became a huge problem for installing python packages

@dimaqq
Copy link
Owner Author

dimaqq commented Mar 24, 2020

Hi Javier!

I think the Linux base doesn't matter here (also I reject the alpine flame). I'm quite sure it's going to be same whether the build base if alpine or ubuntu.

I think, the cause is poetry: as long as I don't distribute compiled wheels (which I should), the C extension needs to be compiled at install time, which explains gcc via build-base. However, the package doesn't use ffi or openssl header files, so why are those needed? I seems poetry's builder somehow needs that...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants