fork issue on macOS
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
When using docker-py with a gunicorn server I get the following crash
objc[99107]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[99107]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
The temporary fix is
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
% uname -a
Darwin ME 19.3.0 Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64
% docker --version
Docker version 19.03.8, build afacb8b
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported docker-py and gunicorn crash on macOS using the versions and uname output in the issue. Trace the fork-related failure to identify whether it belongs in docker-py, and consider the issue complete when the cause and supported resolution are established and covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100