Greenlight ERROR: Couldn't find env file: /root/greenlight/.env

[David Heuring]

I already had Greenlight 2.0 installed but decided to update it so I re-ran all the upgrade commands but now I can't access the Greenlight home page.  I get a 400 error.  When I try to run docker-compose up -d, I get this - ERROR: Couldn't find env file: /root/greenlight/.env.  I know the env is in that directory because I have added the required information to it. I followed all the upgrade 1.0 to 2.0 steps in the manual exactly as they are presented.  

Thanks,

Dave 

[David Heuring]

Update: So I removed the Greenlight docker container and tried to do a clean install from scratch.  Got the same result.  Everything looks fine until I run docker-compose up -aI checked the "docker-compose.yml" and I see it is looking for a .env file which of course doesn't exist.  There's only the docker-compose.yml and env files in the Greenlight directory.  Can anyone tell me what's happening here?

Much appreciated!

Dave

[satyakam goswami]

On Thu, Apr 18, 2019 at 11:51 AM David Heuring <da...@heuring.us> wrote:

Update: So I removed the Greenlight docker container and tried to do a clean install from scratch.  Got the same result.  Everything looks fine until I run docker-compose up -aI checked the "docker-compose.yml" and I see it is looking for a .env file which of course doesn't exist.  There's only the docker-compose.yml and env files in the Greenlight directory.  Can anyone tell me what's happening here?

this is what worked for me , i checked out the latest code from Github

cd ~/greenlight

docker run --rm bigbluebutton/greenlight:v2 cat ./sample.env > env

then followed the steps from http://docs.bigbluebutton.org/install/greenlight-v2.html#3-configure-greenlight the env file you create should have all the variables before you start docker image

 

i used docker run command and followed the followinf commands from documentation

To run Greenlight using docker run, from the ~/greenlight directory, run the following command:

docker run --restart unless-stopped -d -p 5000:80 -v $(pwd)/db/production:/usr/src/app/db/production --env-file env --name greenlight-v2 bigbluebutton/greenlight:v2

thanks,

-Satya

Satyakam.dev | afrost.org | fossevents.in

** For all official purposes use my name as Satyakam Goswami **

 

Much appreciated!

Dave

On Thursday, April 18, 2019 at 9:36:04 AM UTC+7, David Heuring wrote:

I already had Greenlight 2.0 installed but decided to update it so I re-ran all the upgrade commands but now I can't access the Greenlight home page.  I get a 400 error.  When I try to run docker-compose up -d, I get this - ERROR: Couldn't find env file: /root/greenlight/.env.  I know the env is in that directory because I have added the required information to it. I followed all the upgrade 1.0 to 2.0 steps in the manual exactly as they are presented.  

Thanks,

Dave 

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[David Heuring]

And here's the contents of docker-compose.yml which shows it is calling the .env file.

version: '3'

services:

  app:

    entrypoint: [bin/start]

    image: bigbluebutton/greenlight:v2

    container_name: greenlight-v2

    env_file: .env

    restart: unless-stopped

    ports:

      - 5000:80

    volumes:

      - ./db/production:/usr/src/app/db/production

      - ./log:/usr/src/app/log

#    logging:

#      driver: $LOG_DRIVER

#      options:

#        syslog-address: $LOG_ADDRESS

#        tag: $LOG_TAG

On Thursday, April 18, 2019 at 9:36:04 AM UTC+7, David Heuring wrote:

[satyakam goswami]

    env_file: .env

    restart: unless-stopped

    ports:

      - 5000:80

    volumes:

      - ./db/production:/usr/src/app/db/production

      - ./log:/usr/src/app/log

#    logging:

#      driver: $LOG_DRIVER

#      options:

#        syslog-address: $LOG_ADDRESS

#        tag: $LOG_TAG

yes it is , did you copy sample.env to a new file named env and make changes to the env file matching your environment , the error is its looking for env file in the present working directory and could not find one 

[David Heuring]

Yes, I did.  I used this command -- docker run --rm bigbluebutton/greenlight:v2 cat ./sample.env > env But it creates an env file not an .env file. The docker-compose.yml file is calling for an .env file which obviously doesn't exisit. I tired adding a "." to the env file. I did not get an error but it did not set up Greenlight like it should the first time you run it.

[David Heuring]

Okay, I guess it did work.  I simply added a "." to the "env" file and then ran docker-compose up -d and it evidently did work because when I went to xxxxxxxxx.xxx/b, the page loaded and everything seems normal.  It seems to me that the Greenlight instructions need to add that dot to the command that creates the "env" file.

[David Heuring]

On second thought, I don't this is the solution.  I'm just wondering why the docker set up is requiring the .env file in the first place.  It's essentially a hidden file this way.  I can't see it but if I use an editor, it opens up.  It's working for me right now but this still doesn't seem right.

[Chad Pilkey]

The name of the environment file just needs to be the same. I'm not sure why they're different in the documentation and the docker-compose file. Neither part has been changed in six months.