GitHub user potiuk edited a comment on the discussion: Scheduler log directory created as root
> Is there an "official" option to have regular security upgrades installed > without re-building and re-deploying airflow? You should rebuild and redeploy your image whenever you have new image - and you can rebuild image as described "officially" here: https://airflow.apache.org/docs/docker-stack/index.html#what-should-i-do-if-my-security-scan-shows-critical-and-high-vulnerabilities-in-the-image This makes completely no sense to run unnattended upgrades daemon inside your image because all the upgrades will be immediately lost when your docker container restarts - including cases where your deploymend decides to restart it - and after restart - until your "upgrade" service will do it's job, your image will run older version of software - more than that - in case you have unattended upgrades that require restart - it's impossible to get them in, because ... you are loosing all changes after restart. So - what you are doing is just wrong. You should have a pipeline to rebuild your image when needed and use the rebuilt image and restart your airflow containers with this new image. Full stop. There is no other way. GitHub link: https://github.com/apache/airflow/discussions/48561#discussioncomment-13755929 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
