Issues with the Docker Run Command...........and solutions
## Alarm system
Magellan MG5050 with IP150

## Environment
Proxmox Virtual Env, Debain 10 VM with Docker

## Git branch
Master

## Describe the bug
The Docker run command gave me a few issues. They may be only related to Debian but posting here to help others

## To Reproduce
1) When I ran the Docker command for pai I received a "permission denied" error message relating to -v /opt/pai/log:/var/log/pai section of the run command. I tried to run as sudo and also change the user within the run command to pai but no luck with either.
            - In order to fix this I added the following to the run command.
              --user="$(id -u):$(id -g)"

2) The logs within my paradox container tended to lose time sync with the host after 5 or so hours. After a day or so they tended to drift to about 7 hours difference to the host.
            - I am still testing this but so far after 2 days I am still in sync after adding the following 
               volume creation to the run command.
              -v /etc/timezone:/etc/timezone:ro -v /etc/localtime:/etc/localtime:ro

3) This one is not an issue but more something to note. The MQTT_BIND_ADDRESS in the pai.conf settings required some thought when using Docker. Because Docker creates its own internal network and NAT, I was unable to use the default loopback (127.0.0.1) for the BIND. I was also not able to use my host IP. Instead I had the use the Paradox container IP address (172.x.x.x), that the docker creates for itself, as the BIND_ADDRESS. Issue with this is that it is not static and will change on a reboot of the host. I am currently playing with the docker network settings to have this statically assigned. If anyone has already come across this please add a comment.


