[BUG] Double take exists immediately (<1s)

[rubenoost]

Describe the bug
The container starts but exists after MQTT connected is printed to console (level:silly)

Version of Double Take
1.7.0-SHA7

Expected behavior
Double take starts

Screenshots

info: Double Take v1.7.0-bf3e911
verbose: {
  auth: false,
  detect: {
    match: {
      save: true,
      base64: false,
      confidence: 60,
      purge: 168,
      min_area: 10000
    },
    unknown: {
      save: true,
      base64: false,
      confidence: 40,
      purge: 8,
      min_area: 0
    }
  },
  time: { timezone: 'UTC' },
  frigate: {
    attempts: { latest: 10, snapshot: 10, mqtt: true, delay: 0 },
    image: { height: 500 },
    labels: [ 'person' ],
    url: 'http://192.168.1.198:5000'
  },
  mqtt: {
    topics: {
      frigate: 'frigate/events',
      matches: 'double-take/matches',
      cameras: 'double-take/cameras',
      homeassistant: 'homeassistant',
      detect: [Object]
    },
    host: '***',
    username: '***',
    password: '********'
  },
  logs: { level: 'silly' },
  ui: {
    path: '',
    theme: 'bootstrap4-dark-blue',
    editor: { theme: 'nord_dark' },
    logs: { lines: 500 },
    pagination: { limit: 50 },
    thumbnails: { quality: 95, width: 500 }
  },
  detectors: { deepstack: { timeout: 15, url: '***' } },
  server: { port: 3000 },
  storage: {
    path: '/config/double-take',
    config: { path: '/config/double-take' },
    secrets: { path: './.storage/config', extension: 'yaml' },
    media: { path: '/media/double-take' },
    tmp: { path: '/dev/shm/double-take' }
  },
  version: '1.7.0-bf3e911'
}
info: MQTT: connected

This is al that is printed before the container exits with status code 1

Hardware

• HassOS 7.0

Additional context
I was able to fix it by removing SECRET_PATH from the config.json for the stable branch.

[thundergreen]

jakowenko/double-take#173

Same issue it's more the Secret_path than config path

[rubenoost]

@thundergreen You are right, it was supposed to say the SECRET_PATH. Fixed it, although it seems my problem is a bit different than yours.