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
Lando doesn't remove services even after a destroy and restar #1237
Comments
I've edited the title of this issue because initially I thought that it was only related to database but I can see that other services remain and restart even when they are removed from the .lando.yml file. |
I am seeing this as well. I tried out an edge_ssl service on one of my projects and then removed it from the .lando.yml. Since then I've destroyed and rebuilt the app many times, removed and reinstalled both Lando and Docker (for other reasons) several times, and I still get
on every build until it gives up. |
+1 |
what is the correct command to also remove the cache from that lando build? |
Lando will automatically clean up orphaned containers in RC2 which should resolve this |
Bug Report
Tell us about your setup
What is your lando version and operating system? (note that the older your version the less likely we are to reply)
v3.0.0-beta.47 on Linux Mint 19 Tara
Tell us about your
.lando.yml
Tell us about the command you were running
After some time I had to remove a database from the configuration. I edited my lando.yml and removed the second database (jailfree_db) as shown below:
Then I ran the following command as suggested here https://docs.devwithlando.io/issues/switching-dbs.html
lando destroy && lando start
Tell us about the error you got
Even after destroying, lando will try to load the database that was removed taking longer time to restart and showing an error.
Rerun the command that produced your error in
verbose
mode. Note thatverbose
mode is run like thislando command -- -vvv
. Paste in the error and the ~100 lines that proceeded it.Tell us generally about your bug
I would expect that Lando wouldn't try to continue using a service that has been removed from the lando.yml file.
Please detail the steps we can take to replicate this bug. Be as detailed as possible.
Example:
Tell us more
Could better documentation have prevented this issue? if so what should we change?
Not sure if I'm missing something. I couldn't find anything in the documentation rather than destroying and restarting. If there is any command that I've missed, please document at https://docs.devwithlando.io/issues/switching-dbs.html
Does this bug prevent you from using lando?
Yes, we have to continuously restart the application and this issue takes a lot of extra time to the point that we are considering doing the development outside of lando.
The text was updated successfully, but these errors were encountered: