It says that images become bigger, slower and as far as PyPI is concerned much more error prone.
So I should maybe change the base image to the python:<version>-slim image.
As https://pythonspeed.com/articles/alpine-docker-python/ points out using alpine images as base for Docker files hosting python projects seems not to be a good choice.
It says that images become bigger, slower and as far as PyPI is concerned much more error prone.
So I should maybe change the base image to the `python:<version>-slim` image.
Tried to use the slim image as base but because of the ffmpeg dependency the build gets really huge as it installs the whole graphical and audio systems. And building takes a looooong time. Seems like I could also use the python or ubuntu images then.
As I have the alpine variant running I stick to that for the moment.
Tried to use the slim image as base but because of the ffmpeg dependency the build gets really huge as it installs the whole graphical and audio systems. And building takes a looooong time. Seems like I could also use the python or ubuntu images then.
As I have the alpine variant running I stick to that for the moment.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As https://pythonspeed.com/articles/alpine-docker-python/ points out using alpine images as base for Docker files hosting python projects seems not to be a good choice.
It says that images become bigger, slower and as far as PyPI is concerned much more error prone.
So I should maybe change the base image to the
python:<version>-slimimage.Tried to use the slim image as base but because of the ffmpeg dependency the build gets really huge as it installs the whole graphical and audio systems. And building takes a looooong time. Seems like I could also use the python or ubuntu images then.
As I have the alpine variant running I stick to that for the moment.