Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Named volume is used in service "proxy" but no declaration was found in the volumes section #927

Closed
legovaer opened this issue Apr 30, 2018 · 6 comments

Comments

Projects
None yet
5 participants
@legovaer
Copy link

commented Apr 30, 2018

Bug Report

Setup

Lando: v3.0.0-beta.42
Docker: Docker version 18.03.1-ce, build 9ee9f40
OS: Mac OS High Sierra (with latest updates on)

.lando.yml:

# Name the application the same as in your .platform.app.yaml.
name: mtdd18
# Use the recipe appropriate for your application.
recipe: drupal8

# The following additional build step will install the Platform CLI
# in the application container.
services:
  appserver:
    build:
      - "curl -sS https://platform.sh/cli/installer | php"

# The following entry creates a `lando platform` command that will run
# any Platform CLI command from inside the container if desired.
tooling:
  cim:
    service: appserver
    description: Import the configuration from the codebase
    cmd:
      - /app/scripts/lando/cim.sh
  cex:
    service: appserver
    description: Export the configuration from the codebase
    cmd:
      - /app/scripts/lando/cex.sh
  platform:
    service: appserver
    description: Run Platform CLI commands
    cmd:
      - /var/www/.platformsh/bin/platform
    options:
      passthrough: true
  sync-db:
    service: appserver
    description: Get the database from a Platform.sh environment
    cmd:
      - /app/scripts/lando/swap-db.sh
    options:
      env:
        passthrough: true
        alias:
          - e
        describe: The environment you want to copy the database from.
        interactive:
          type: input
          message: Which environment would you like to copy?
          default: master
          wieght: 600

config:
  # Lando defaults to Apache. Switch to nginx to match Platform.sh.
  via: nginx

  # Set the webroot to match your .platform.app.yaml.
  webroot: web

  # Lando defaults to the latest MySQL release, but Platform.sh uses MariaDB.
  # Specify the version to match what's in services.yaml.
  database: mariadb:10.1

Issue

After updating to the latest version of Lando, now I get an error when executing lando start:

error: Error: Named volume "$LANDO_ENGINE_CONF:/lando:rw" is used in service "proxy" but no declaration was found in the volumes section.

Edit1: I went back to version v3.0.0-beta.40 and now it's working again.

@kcaulkins

This comment has been minimized.

Copy link

commented Apr 30, 2018

I had the same thing with version 42. Try deleting ~/.lando folder and try again, it worked for me.

@raubin

This comment has been minimized.

Copy link

commented Apr 30, 2018

I would not recommend deleting the entire ~/.lando folder, as there's some useful configuration there. Just delete the ~/.lando/proxy folder, since that's the only folder related to this specific issue. You could even try deleting just the proxy files within that directory for the ones that you're having trouble starting.

@JuanGongora

This comment has been minimized.

Copy link

commented Apr 30, 2018

@raubin Thank you, your resolution worked for me using version v3.0.0-beta.42

@pirog

This comment has been minimized.

Copy link
Member

commented May 1, 2018

@legovaer i havent been able to replicate this yet but it sounds like

  1. Spinning up a proxy on older lando version
  2. Switching to beta.42

Might be the steps. If that is the case i'm guessing we can bake in a better solution here.

@pirog

This comment has been minimized.

Copy link
Member

commented May 1, 2018

Alright i can definitely confirm this with steps above. Hotfix incoming!

@pirog pirog referenced this issue May 1, 2018

Merged

Fixes #922 #923

@pirog pirog self-assigned this May 2, 2018

@pirog pirog added the bug label May 2, 2018

@pirog pirog added this to the 3.0.0-beta.43 milestone May 2, 2018

pirog added a commit that referenced this issue May 2, 2018

@pirog

This comment has been minimized.

Copy link
Member

commented May 2, 2018

alright, about to roll hotfix release with this fix in it!

@pirog pirog closed this May 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.