potiuk commented on issue #17546: URL: https://github.com/apache/airflow/issues/17546#issuecomment-897731840
Hmm. Then I guess the bug is in one of the libraries added: `gconf-service libasound2 libatk1.0-0 libcairo2 libcups2 libfontconfig1 libgdk-pixbuf2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libxss1 fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget libappindicator3-1 libgbm1` I am afraid then then either you try to investigate which one causes it by selective disabling some, or you will have to live with the LD_PRELOAD workaround. BTW. Maybe another thing you can try. You can try to follow the customization route rather than image extension. It is a bit involved (you need to use airflow sources to build the image) but at the end you will get the image which will be ~400 MB smaller. With your current approach, you add build-essentials in order to add certain packages (I guess) but if you go with the customisation route, you will not have to do it, and then in your final package you need to only add "runtime" libraries, rather thant development counter-parts. This should not have impact on the bug, but a chance is that something in the "build enabled environment" triggers the bug, rather than one of your libraries. You can find some examples and guidelines in https://airflow.apache.org/docs/docker-stack/build.html#customizing-the-image -maybe, when you go "custom-image" route, the problem will go away without having to use the LD_PRELOAD workaround? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
