Rick Bartra 9eb430566b Make airflow-worker containers non-privileged ... The 'airflow-worker' and 'airflow-logrotate' containers do not need to run as privileged containers to perform their jobs. Shipyard deploy_site action was used to test the 'airflow-worker' as a deploy_site invokes 'airflow-worker'. When performing deploy_site action, all steps succeeded and the 'airflow-worker' shows no errors when 'airflow-worker' is non-privileged. When 'airflow-logrotate' runs as non-privileged, the 'airflow-logrotate' container still logs correctly and is able to delete/rotate logs without problems. Note: Making airflow-worker run with non-privileged containers means that these containers will use the docker-default apparmor profile by default. Change-Id: I26eda3eb8b7a36e67c2e7b593326f1d063600fc3		2018-09-27 15:14:20 -04:00
..
shipyard	Make airflow-worker containers non-privileged	2018-09-27 15:14:20 -04:00