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

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

Closed
digisavvy opened this Issue Nov 16, 2018 · 12 comments

Comments

Projects
None yet
10 participants
@digisavvy
Copy link

digisavvy commented Nov 16, 2018

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

This comment has been minimized.

Copy link

jimshreds commented Nov 19, 2018

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

This comment has been minimized.

Copy link

jimshreds commented Nov 19, 2018

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

This comment has been minimized.

Copy link
Author

digisavvy commented Nov 20, 2018

That worked for me, too. Thank you!

@digisavvy digisavvy closed this Nov 20, 2018

@darthsteven

This comment has been minimized.

Copy link

darthsteven commented Nov 20, 2018

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 digisavvy reopened this Nov 20, 2018

@digisavvy

This comment has been minimized.

Copy link
Author

digisavvy commented Nov 20, 2018

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

This comment has been minimized.

Copy link

tmountjr commented Nov 26, 2018

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 comment has been minimized.

Copy link
Contributor

nathandentzau commented Nov 26, 2018

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:

screen shot 2018-11-26 at 12 09 26 am

@johnpicozzi

This comment has been minimized.

Copy link

johnpicozzi commented Nov 27, 2018

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.
image

Hope this helps!

@pirog pirog added this to the RC1 milestone Nov 28, 2018

@pirog pirog self-assigned this Nov 28, 2018

@astolfivincent

This comment has been minimized.

Copy link

astolfivincent commented Dec 20, 2018

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 comment has been minimized.

Copy link
Member

pirog commented Jan 13, 2019

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

@pirog pirog closed this Jan 13, 2019

@dgpalmer

This comment has been minimized.

Copy link

dgpalmer commented Jan 24, 2019

Hi Mike,

When will RC2 come out?

Thanks!

@ccharlton

This comment has been minimized.

Copy link
Contributor

ccharlton commented Jan 24, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment