docker_systemd_service/molecule/with_custom_flags/group_vars/all.yml

---
docker_systemd_service_container_name: "nginx"
docker_systemd_service_image: nginx:1.27
docker_systemd_service_container_env:
  TEST_ENV: test
docker_systemd_service_container_pull_image: false
docker_systemd_service_container_pull_force_source: false
docker_systemd_service_flags:
  - privileged
  - network: host
  - cap-add:
      - NET_ADMIN
docker_systemd_service_container_cmd: []
docker_systemd_service_name: "{{ docker_systemd_service_container_name }}_container"
docker_systemd_service_systemd_options: []
docker_systemd_service_start: false
feat(tests): added custom tests for both vagrant and docker 2023-12-10 17:25:43 +00:00			`---`
			`docker_systemd_service_container_name: "nginx"`
ci: fix custom flags tests, add different image values 2024-11-09 13:06:07 +00:00			`docker_systemd_service_image: nginx:1.27`
feat(tests): added custom tests for both vagrant and docker 2023-12-10 17:25:43 +00:00			`docker_systemd_service_container_env:`
			`TEST_ENV: test`
			`docker_systemd_service_container_pull_image: false`
			`docker_systemd_service_container_pull_force_source: false`
			`docker_systemd_service_flags:`
			`- privileged`
			`- network: host`
			`- cap-add:`
			`- NET_ADMIN`
			`docker_systemd_service_container_cmd: []`
			`docker_systemd_service_name: "{{ docker_systemd_service_container_name }}_container"`
			`docker_systemd_service_systemd_options: []`
feat: only allow starting and managing running services. destroying/removing services should be handled separately, most likely by the end user's custom code, to avoid data loss, etc... 2024-11-09 12:24:14 +00:00			`docker_systemd_service_start: false`