Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Umami - Failed container start with environment variables

Scheduled Pinned Locked Moved Solved Umami
6 Posts 5 Posters 222 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    echokos
    wrote on last edited by
    #1

    Adding any environment variables to the env file and then restarting the container causes the app to never start.

    For example - on a new install, add FORCE_SSL = 1 to the env file and restart the container. The error log contains:

    May 24 20:30:40 /app/data/env: line 5: FORCE_SSL: command not found
    May 24 20:31:41 ==> Changing ownership
    May 24 20:31:41 => Building database
    May 24 20:31:41 /app/data/env: line 5: FORCE_SSL: command not found
    May 24 20:32:41 ==> Changing ownership
    May 24 20:32:41 => Building database
    May 24 20:32:41 /app/data/env: line 5: FORCE_SSL: command not found
    

    And it will continually stay in this state creating the errors forever until the container is stopped.

    robiR 1 Reply Last reply
    0
  • robiR Offline
    robiR Offline
    robi
    replied to echokos on last edited by
    #2

    @echokos Sounds like a packaging bug. @staff will find it.

    Life of sky tech

    1 Reply Last reply
    1
  • nebulonN nebulon marked this topic as a question on
  • N Offline
    N Offline
    Neiluj
    wrote on last edited by Neiluj
    #3

    @echokos said in Umami - Failed container start with environment variables:

    May 24 20:32:41 /app/data/env: line

    I had something similar with IGNORE_IP when I lazily copied the variable from the umami doc (https://umami.is/docs/environment-variables)

    try this FORCE_SSL=1 (without spaces)

    and restart your app - This seems to work.

    E 32463 2 Replies Last reply
    3
  • E Offline
    E Offline
    echokos
    replied to Neiluj on last edited by
    #4

    @Neiluj That sure is the issue. @staff - maybe just adding a note in the Cloudron docs would be enough for this issue.

    1 Reply Last reply
    1
  • nebulonN Online
    nebulonN Online
    nebulon Staff
    wrote on last edited by
    #5

    For background, that file is source /app/data/env in the start.sh so it has to be a valid shell script. Such a behavior is happening in many apps, not sure how to document this or if we can add some extra trimming/filtering for such cases?

    1 Reply Last reply
    0
  • 32463 Offline
    32463 Offline
    3246
    replied to Neiluj on last edited by
    #6

    @Neiluj thank you! That fixed it for me 🙂

    Visit https://www.bebravernow.com for more

    1 Reply Last reply
    0
  • nebulonN nebulon has marked this topic as solved on

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.