Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-6715

docker-compose command does not work anymore

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • 1

    Description

      Trying to set the DBs up with docker, following this documentation https://aerogear.org/docs/unifiedpush/ups_userguide/index/#Docker-databases, now throws an error due to file name:

      $ ls
      ups-datasource.yml
      
      $ docker-compose up -d
      ERROR: 
              Can't find a suitable configuration file in this directory or any
              parent. Are you in the right directory?
      
              Supported filenames: docker-compose.yml, docker-compose.yaml
      
      

      And it's not even possible to specify the name of a file by using `-f name.yml`:

      $ docker-compose up -d -f ups-datasource.yml
      Builds, (re)creates, starts, and attaches to containers for a service.
      
      Unless they are already running, this command also starts any linked services.
      
      The `docker-compose up` command aggregates the output of each container. When
      the command exits, all containers are stopped. Running `docker-compose up -d`
      starts the containers in the background and leaves them running.
      
      If there are existing containers for a service, and the service's configuration
      or image was changed after the container's creation, `docker-compose up` picks
      up the changes by stopping and recreating the containers (preserving mounted
      volumes). To prevent Compose from picking up changes, use the `--no-recreate`
      flag.
      
      If you want to force Compose to stop and recreate all containers, use the
      `--force-recreate` flag.
      
      Usage: up [options] [SERVICE...]
      
      Options:
          -d                         Detached mode: Run containers in the background,
                                     print new container names.
                                     Incompatible with --abort-on-container-exit.
          --no-color                 Produce monochrome output.
          --no-deps                  Don't start linked services.
          --force-recreate           Recreate containers even if their configuration
                                     and image haven't changed.
                                     Incompatible with --no-recreate.
          --no-recreate              If containers already exist, don't recreate them.
                                     Incompatible with --force-recreate.
          --no-build                 Don't build an image, even if it's missing.
          --build                    Build images before starting containers.
          --abort-on-container-exit  Stops all containers if any container was stopped.
                                     Incompatible with -d.
          -t, --timeout TIMEOUT      Use this timeout in seconds for container shutdown
                                     when attached or when containers are already
                                     running. (default: 10)
          --remove-orphans           Remove containers for services not
                                     defined in the Compose file
      
      

      So it's necessary to rename the file to `docker-compose.yml`.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jgallaso Jose Miguel Gallas Olmedo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: