Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-3605

"-d" option to demo script fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: (None)
    • Resolution: Unresolved
    • Affects Version/s: 2.4.0b1
    • Fix Version/s: None
    • Labels:
    • Days in progress:
      0

      Description

      Using the "-d" option fails with

      $ ./demo -f docker-compose.enterprise.yml up -d
      Starting the Mender demo environment...
      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
      

      It does work if you omit the "-d"

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              drewmoseley Drew Moseley
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Summary Panel