latest postgres docker image update fails #1612
Bitnami changed the config of their postgres container: https://github.com/bitnami/bitnami-docker-postgresql#notable-changes
This makes postgres installs fail.
name: test recipe: lamp config: php: '7.2' database: postgres
It will fail to start and the logs show a failure to start the entrypoint.
Remove any existing postgres images to ensure lando downloads the latest container.
$ lando start ... Starting test_database_1 ... done ERROR: No container found for database_1 error: Looks like database is not running! It should be so this is a problem. warn: Try running `lando logs -s database` to help locate the problem!
$ lando logs -s database Attaching to test_database_1 database_1 | mkdir: cannot create directory ‘/etc/ssh’: Permission denied database_1 | Running command /app-entrypoint.sh /run.sh database_1 | Running with exec! database_1 | /lando-entrypoint.sh: 26: exec: /app-entrypoint.sh: not found database_1 | mkdir: cannot create directory ‘/etc/ssh’: Permission denied database_1 | Running command /app-entrypoint.sh /run.sh database_1 | Running with exec! database_1 | /lando-entrypoint.sh: 26: exec: /app-entrypoint.sh: not found
name: test recipe: lamp config: php: '7.2' database: postgres:10.6.0-r68
I'm seeing the sameon both 10.7.0 and 9.6, although the workaround doesn't appear to work with either of the following .lando.yml files for 3.0.0-rc.16 on windows 10 pro for workstations.
If I try to use v10.6.0 instead, lando start finishes with
referenced this issue
May 9, 2019
Actually I think that may have to do with the "services" .lando.yml syntax recommended in the docs. I get that issue when using
but not when using
...although port forwarding doesn't work in the second example. Probably the wrong way to define it.
Think it warrants a separate issue?
That seems to have worked @pirog, thanks! However, note that the correct path is
Also note, that I had to still specify
End result: this workaround worked for me:
@pirog I didn't expect portforward to work, just wanted to note that it didn't. Didn't realize it was service specific but that makes. By "Think it warrants a separate issue?" I was referring to the issue with the service syntax not working with @JorisVanEijden workaround. I see now that that wasn't at all clear.
Can confirm that @jcandan .lando.yml worked for me as well. Thanks everybody!
When I apply the workaround in here #1612 (comment)
I get this issue: