Skip to content

SEGFAULT when certain modules are used in a project with Alpine 3.6/Python 3.6 #211

Closed
@beaugunderson

Description

@beaugunderson

We've recently upgraded several of our containers to Python 3.6.

Some of the containers always segfault immediately after starting Django's runserver command.

In a couple of the containers upgrading our dependencies fixed the issue, but on some of the other containers that didn't have the issue upgrading the dependencies caused it to start happening.

In one example upgrading requests from 2.12.1 to 2.18.1 stopped the SEGFAULTs but adding the latest version of boto3 caused them to start again.

The issue only happens when run under docker.

I have a simple example repo here and would like to offer a bounty of $100 to whoever can either fix the issue or explain it in a way that allows me to fix it. ✨

Edit: we've tested with 3-alpine and 3-alpine3.6; same result.

Also SEGFAULTs on 3.6.2rc2-alpine3.6.

More clues: requests is also implicated in boto3 which includes botocore--which includes a vendored requests 2.7.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions