Error when trying to move to a custom Greenlight: ### ... because CD_DOCKER_USERNAME or CD_DOCKER_PASSWORD are missing

[Carl Gosselin]

Hello - I'm getting this strange error when attempting to turn greenlight into a custom greenlight with the latest BBB/Greenlight...

#### Docker image for greenlight_lumened can't be published because CD_DOCKER_USERNAME or CD_DOCKER_PASSWORD are missing (Ignore this warning if running outside a CD/CI environment)

I have customized greenlight in the past using Docker Run and never had this type of issue.  It's also my first time using './scripts/image_build.sh' to build the image.  I took a look at the image_build.sh file and I don't really understand it's purpose.  Seems like I have to create some sort of Docker account?

There seems to be 2 documents that provides steps to be able to customize Greenlight and I seem to be jumping back and forth between steps:

1. http://docs.bigbluebutton.org/greenlight/gl-customize.html

2. http://docs.bigbluebutton.org/greenlight/gl-customize.html#customizing-greenlight

Can anyone help clarify how to avoid the CD_DOCKER_USERNAME message/error?

[Carl Gosselin]

I'm stuck.  Need help.  I've made multiple attempts to switch to a custom version of greenlight but can't seem to make it work.

I previously used docker run commands in previous releases to make it work and now I can't seem to do the same with docker-compose.

Below are all of my steps with the final error at the moment.  I'm hoping someone can help.

main script -> Switching from Install to Customize

link: https://docs.bigbluebutton.org/greenlight/gl-install.html

Step 1 - in the freshly installed greenlight folder, I brought down the docker container

$ docker-compose down

Step 2 - I then renamed the freshly installed greenlight

$ cd ..

$ mv greenlight/ greenlight-old/ 

In following the documentation, I'm redirected to another page to customize greenlight

link:  https://docs.bigbluebutton.org/greenlight/gl-customize.html#customizing-greenlight

Step 3 - Install Docker (I skipped this step as Docker is already installed)

$ docker -v 

output: Docker version 19.03.8, build afacb8b7f0

Step 4 - Install Greenlight

4a. Fork Greenlight repository into my GitHub account

4b.  Clone repository on my AWS server

                $ git clone https://blahblah…

4c.   $ cd greenlight

4d.   $ git status  (yes, looks good)

4e.   $ git remote add upstream https://github.com/bigbluebutton/greenlight.git

4f.    $ git remove -v  (yes, looks good)

4g.   $ git fetch upstream

4h.   $ git checkout -b custom-changes upstream/v2 (ok, now on a branch)

Step 5 - Configure Greenlight

$ cp sample.env .env

Step 6 - Generate secret key

$ docker run --rm bigbluebutton/greenlight:v2 bundle exec rake secret

(updated .env file with secret)

Step 7 - Set up BBB credentials

$ bbb-conf --secret

(updateed .env file with BBB endpoint and secret)

Step 8 - Verify .env file

        $ docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check

(yes, all 3 passed)

Step 9 - . Configure NGINX to route to greenlight

$ cat ./greenlight.nginx | sudo tee /etc/bigbluebutton/nginx/greenlight.nginx

$ systemctl restart nginx

Step 10 -  Add option to add default landing page to root of server

/etc/nginx/sites-available/bigbluebutton

location = / {

  return 307 /b;

}

Step 11 - . restart NGINX

$ systemctl restart nginx

section: Start Greenlight

Step 12 - Verify docker-compose

$ docker-compose -v

         output: docker-compose version 1.24.0, build 0aa59064

Step 13 - Create docker image…

./scripts/image_build.sh custom_greenlight release-v2

Some of the output…

#### Docker image custom_greenlight:release-v2 is being built

Sending build context to Docker daemon   4.32MB

Step 1/27 : FROM ruby:2.5.1-alpine AS base

…

Successfully built fff43bba5b0f

Successfully tagged custom_greenlight:release-v2

#### Docker image for custom_greenlight can't be published because CD_DOCKER_USERNAME or CD_DOCKER_PASSWORD are missing (Ignore this warning if running outside a CD/CI environment)

Step 14 -  update docker-compose file with

services:

  app:

    entrypoint: [bin/start]

    image: custom_greenlight:release-v2

Step 15 - in greenlight, bring down docker

$ docker-compose down

Step 16 - then bring docker image up

$ docker-compose up -d

output - final error messages...

Creating network "greenlight_default" with the default driver

Pulling app (custom_greenlight:v2)...

ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]

Step 17 - I said ‘y’

Pulling app (custom_greenlight:v2)...

ERROR: pull access denied for custom_greenlight, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Now I’m stuck.  I've tried so many times.  Please help.

[Ahmad Farhat]

Hi Carl,

You can ignore the "Docker image for custom_greenlight can't be published..." error

Pulling app (custom_greenlight:v2)...

Doesn't look like you updated your docker-compose.yml correctly. Instead of setting image: custom_greenlight:release-v2, it looks like you set it to image: custom_greenlight:v2. Can you send me the contents of your docker-compose.yml?

[Carl Gosselin]

Thank you so much Ahmad.  That fixed it.

[Alain Lauzon]

How did you fix it? I am still having the same issue as you had.
I did:

./scripts/image_build.sh meeting release-v2

then my docker-compose file contains

cat docker-compose.yml
version: '3'

services:
  app:
    entrypoint: [bin/start]
    image: meeting:release-v2
    container_name: greenlight-v2
    env_file: .env
    restart: unless-stopped
    ports:
      - 127.0.0.1:5000:80
# When using external logging
#    logging:
#      driver: $LOG_DRIVER
#      options:
#        syslog-address: $LOG_ADDRESS
#        tag: $LOG_TAG
    volumes:
      - ./log:/usr/src/app/log
      - ./storage:/usr/src/app/storage
# When using sqlite3 as the database
#      - ./db/production:/usr/src/app/db/production
# When using postgresql as the database
    links:
      - db
  db:
    image: postgres:9.5
    restart: unless-stopped
    ports:
      - 127.0.0.1:5432:5432
    volumes:
      - ./db/production:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=password

And when I do docker-compose up -d
Pulling app (meeting:release-v2)...

ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]y
Pulling app (meeting:release-v2)...
ERROR: pull access denied for meeting, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

What can I do to make it work?