You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm reopening this issue again (I can't reopen the original) because I have news and there is actually a BUG that must be fixed.
Note
For more context on what's going on, take a look at the original issue: #309
If I use docker-compose down and then docker-compose up -d then everything works as expected and the file is not changed back to defaults;
If I use docker-compose restart the file IS ACTUALLY rewritten with the default values, losing all customizations;
If I have a power outage, when the container starts, the file IS ACTUALLY rewritten with the default values, losing all customizations.
✔️ The first point is (obviously) not a problem because it is the expected behavior
✖️ The second point is a problem but there is a workaround, don't run that command
❌ The third point is a MAJOR problem and happens because docker compose is a service that starts at machine startup, and the container definition declares restart: unless-stopped
For context, this is my docker-compose yaml:
version: '3.9'services:
(...)other services(...)asterisk:
container_name: asteriskimage: ghcr.io/tech7fox/asterisk-hass-addon:mainbuild:
context: ./asterisktty: truenetwork_mode: hostenvironment:
TZ: 'Europe/Lisbon'# Required to get the list of persons from Home AssistantHA_TOKEN: "--REDACTED--"HA_URL: 'https://xxxx.xxx.com'dns:
- 192.168.1.2
- 8.8.8.8
- 8.8.4.4volumes:
- /srv/homeassistant/config/asterisk:/config
- /srv/homeassistant/config/www/sounds:/media
- /srv/homeassistant/config/ssl:/sslrestart: unless-stopped(...)other services(...)
The text was updated successfully, but these errors were encountered:
I'm reopening this issue again (I can't reopen the original) because I have news and there is actually a BUG that must be fixed.
Note
For more context on what's going on, take a look at the original issue:
#309
docker-compose down
and thendocker-compose up -d
then everything works as expected and the file is not changed back to defaults;docker-compose restart
the file IS ACTUALLY rewritten with the default values, losing all customizations;✔️ The first point is (obviously) not a problem because it is the expected behavior
✖️ The second point is a problem but there is a workaround, don't run that command
❌ The third point is a MAJOR problem and happens because docker compose is a service that starts at machine startup, and the container definition declares
restart: unless-stopped
For context, this is my docker-compose yaml:
The text was updated successfully, but these errors were encountered: