Open jasloe opened 1 year ago
@jasloe A colleague of mine experiences the same problem with lando 3.6.5. A temporary downgrade to 3.6.4 might help.
@aimfeld thanks for replying. I'm now running 3.6.4 with mixed results. It seems to work fixing only one of the ports, i.e.:
services:
db:
portforward: 3309
db2:
portforward: 3310
internal_connection: { host: 'db', port: '3306' },
external_connection: { host: '127.0.0.1', port: '50907' },
internal_connection: { host: 'db2', port: '3306' },
external_connection: { host: '127.0.0.1', port: '3310' },
It's unpredictable which service's port gets fixed. Not sure where to go next with troubleshooting.
This issue is still persistent with v3.11.0.
Fix this y’all.
I’m having trouble locking down ports using the platformsh recipe with multiple database containers.
I'm on the latest versions of Lando and the platformsh CLI. Here are the relevant excerpt from my configuration:
lando rebuild -y
returns:There's a nearly identical and now-closed issue at #39. Either there's a regression somewhere or I don't know what I'm doing. Trying to understand the lando logs commands to troubleshoot this but the docs are 404.