Lando MySQL connection does not persist between stop/start of containers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
If I use Lando default config (e.g. lando init), ".lando.yml" looks like this:
name: wp-app
recipe: wordpress
config:
webroot: .
Everything works on first containers running.
But after lando stop and lando start, the data from MySQL does not persist.
If I add database: mysql to the ".landa.yml":
name: wp-app
recipe: wordpress
config:
webroot: .
database: mysql
The data persist between container stop/start.
Am i missing something obvious or is this a bug?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the default .lando.yml produced by lando init and compare it with the version that explicitly sets database: mysql. Reproduce the issue with lando stop followed by lando start; done means the default WordPress recipe retains MySQL data without requiring the extra database setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, wordpress
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100