-
Notifications
You must be signed in to change notification settings - Fork 43
Open
Description
I had the following container_run_args which led to the service not being able to start.
container_run_args: >-
--rm
-p 8080:8080 -p 8443:8443 -p 3478:3478/udp -p 10001:10001/udp
-v "{{ exported_container_volumes_basedir }}/unifi:/unifi:Z"
--hostname="unifi.{{ domain }}"
--memory=2048M
-e TZ="{{ rodhouse_timezone }}"
#-e UNIFI_UID="{{ unifi_uid }}"
#-e UNIFI_GID="{{ unifi_gid }}"
This commented out UID and GID caused the container not to start. Perhaps handlers should be flush then check if the service is running, fail the play if the service isn't running.
Metadata
Metadata
Assignees
Labels
No labels