error: (HTTP code 404) no such container - No such container:

[digisavvy]

Bug Report

Tell us about your setup

Lando Version: v3.0.0-rc.1

Mac OSx Version: 10.14 Mojave

Tell us about your .lando.yml

There is none.

Tell us about the command you were running

I ran lando init pantheon to initiate a new app creation for a WordPress hosted on Pantheon. I received the following output:

? Choose a Pantheon account my@email.com
? Which site? cloudsponge
Starting landoinitcloudsponge_util_1_3494c4dd07ed ... done
Starting landoinitcloudsponge_util_1_3494c4dd07ed ... done
error: (HTTP code 404) no such container - No such container: landoinitcloudsponge_util_1 
alexanders-MacBook-Pro-2:cloud-sponge alex-vasquez$ 

Tell us more

I also tried the following commands:

• In terminal i typed docker ps -a and did find a docker container with cloudsponge. I then ran docker stop [container_name] and then ran docker rm [container_name] which removed the container. I tried re-running the init command again and I still received the same error. There is also no config files and no log files.

The site i'm working with on Pantheon has a live environment, too. Not sure what's weird about this install.

[jimshreds]

Getting error after updating Docker Desktop this morning.

Docker Desktop Version 2.0.0.0-mac78 (28905) Lando v3.0.0-rc.1 OSX 10.13.6 lando.yml: name: dfh recipe: drupal7 config: webroot: .

tried rebuild and destroy and still errors on lando start.

[jimshreds]

downloaded previous version of Docker Desktop : https://docs.docker.com/docker-for-mac/release-notes/

lando rebuild a few times and am back up and running

[digisavvy]

That worked for me, too. Thank you!

[darthsteven]

I imagine this is error was because of the change in naming containers created by Docker compose in 1.23.0:

. The default naming scheme for containers created by Compose in this version has changed from to _, where is a randomly-generated hexadecimal string. Please make sure to update scripts relying on the old naming scheme accordingly before upgrading.

So I think lando will have to change and fix this, rather than getting everyone to stay with an older version of docker compose.

@digisavvy any chance you could re-open this issue please?

[digisavvy]

Done and done. @dustinleblanc and @pirog can you all take a look when you get a chance? I remedied this issue with the fix proposed here but I think it deserves a closer look.

[tmountjr]

For anyone in the same situation as @digisavvy and @jimshreds, I discovered a shortcut to clearing out your broken builds - go into your ~/.lando folder, delete any files or folders named the same as the one that was giving you an error, then build again. Simply destroying doesn't quite get everything but my experience was that deleting those files (at least the ones in the compose folder) let me get up and running quickly.

[nathandentzau]

This actually looks like a bug in RC1. I do not get this error rolling back Lando to Beta 47. Here are my docker versions:

[johnpicozzi]

I can confirm I was having the same issue. downgrading to Beta 47 worked for me as well.

Used the following to install Beta 47 again via brew brew cask install https://raw.githubusercontent.com/Homebrew/homebrew-cask/645dbb8228ec2f1f217ed1431e188687aac13ca5/Casks/lando.rb

Also noticed on the install that worked that it was able to create a cert and that seems to be where it failed before.

Hope this helps!

[vastolf]

This is happening to me to too after updating from docker 17.12.0-mac55 to 2.0.0.0-mac78

I'm getting the following error:

Looks like one of your build steps failed with Error: (HTTP code 404) no such container - No such container: project_appserver_1 

Upon a lando rebuild/start it starts an appserver that is named project_appserver_1_a17c78ef8c82, and I'm fairly certain that docker wasn't adding those hexadecimal strings to the containers before -- more evidence that supports @darthsteven's idea of what's happening here:

I imagine this is error was because of the change in naming containers created by Docker compose in 1.23.0:

. The default naming scheme for containers created by Compose in this version has changed from to _, where is a randomly-generated hexadecimal string. Please make sure to update scripts relying on the old naming scheme accordingly before upgrading.

So I think lando will have to change and fix this, rather than getting everyone to stay with an older version of docker compose.

@digisavvy any chance you could re-open this issue please?

[pirog]

This should all be fixed and compatible with the latest docker/docker-compose when we ship RC2 so going to close for now

[dgpalmer]

Hi Mike,

When will RC2 come out?

Thanks!

[ccharlton]

Shhhh! @dgpalmer If you ask, it goes back into its hole.

[yuseferi]

the same issue after updating docker version No such container: landoproxyhyperion5000gandalfedition_proxy_1

[mdmattin]

Also having this issue after updating to Docker Version 19.03.5, with Lando Version v3.0.0-rc.22.

Error: Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1 at container.(anonymous function).catch.err (/snapshot/lando/build/cli/lib/docker.js:0:0) at runCallback (timers.js:696:18) at tryOnImmediate (timers.js:667:5) at processImmediate (timers.js:649:5) From previous event: at containerOpt (/snapshot/lando/build/cli/lib/docker.js:0:0) at Landerode.remove (/snapshot/lando/build/cli/lib/docker.js:0:0) at exports.destroy.datum (/snapshot/lando/build/cli/lib/router.js:0:0) at Promise.each.Promise.retry (/snapshot/lando/build/cli/lib/router.js:0:0) at Promise.resolve.then.Promise.try (/snapshot/lando/build/cli/lib/promise.js:0:0) From previous event: at rec (/snapshot/lando/build/cli/lib/promise.js:0:0) at Promise.resolve.then.Promise.try.fn.catch.Promise.delay.then (/snapshot/lando/build/cli/lib/promise.js:0:0) at ontimeout (timers.js:427:11) at tryOnTimeout (timers.js:289:5) at listOnTimeout (timers.js:252:5) at Timer.processTimers (timers.js:212:10)

[mdmattin]

Updating to Lando Version v3.0.0-rc.23 fixed this problem. I guess the takeaway is don't update Docker independently of Lando.

[yuseferi]

@maddentim I updated both, but the issue was there. I tried on Mac Catalina 10.15.2

[mlopezcoria]

I'm having this same issue using Lando v3.4.2 and Docker v20.10.9 I tried what @tmountjr suggested, but it didn't work. And also I get lots of Waiting until database service is ready... messages

lando version: v3.4.2 docker version: Docker version 20.10.9, build c2ea9bc90b docker-compose version: Docker Compose version 2.0.1

.lando.yml

name: plugintest
recipe: wordpress
config:
  webroot: public_html/
  php: '7.4'
  database: mariadb:10.5
services:
  pma:
    type: phpmyadmin
    hosts:
      - database
proxy:
  pma:
    - pma.plugintest.lndo.site

[pavel-ruban]

got same issue on Archlinux, lando v3.4.2, docker version 20.10.10 did lot of tricks, rebuilds etc, downgraded lando to 3.1.4 nothing worked, then downgraded docker-compose from community repo

Repository      : community
Name            : docker-compose
Version         : 2.0.1-1

to aur

:: Querying AUR...
Repository      : aur
Name            : docker-compose-bin
Keywords        : docker
Version         : 1.29.2-1

did lando rebuild & dash/underscore container names problem finally got solved, docker itself & lando versions rolled back to same as in the first sentence, the latest ones on Arch.

[wrg20]

For anyone in the same situation as @digisavvy and @jimshreds, I discovered a shortcut to clearing out your broken builds - go into your ~/.lando folder, delete any files or folders named the same as the one that was giving you an error, then build again. Simply destroying doesn't quite get everything but my experience was that deleting those files (at least the ones in the compose folder) let me get up and running quickly.

This worked for me. I just deleted my app folder in ~/.lando and then did a lando start again after updating my docker desktop install.