You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't software versions, but the spec version of a file that we only use on our environments.
And docker compose ignores this since v2, and always uses the latest spec available.
time="2024-12-03T19:23:04+01:00" level=warning msg="/home/penyaskito/Projects/Work/Lullabot/mjff/.ddev/docker-compose.memcached.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
time="2024-12-03T19:23:04+01:00" level=warning msg="/home/penyaskito/Projects/Work/Lullabot/mjff/.ddev/docker-compose.selenium.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
time="2024-12-03T19:23:04+01:00" level=warning msg="/home/penyaskito/Projects/Work/Lullabot/mjff/.ddev/docker-compose.solr.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
File is at drainpipe-dev/scaffold/nightwatch/docker-compose.selenium.yaml
If the scaffolded file is committed to the repo and it's producing conflicts, a workaround is adding to composer.json:
Fixes warns on ddev start.
This isn't software versions, but the spec version of a file that we only use on our environments.
And docker compose ignores this since v2, and always uses the latest spec available.
File is at
drainpipe-dev/scaffold/nightwatch/docker-compose.selenium.yaml
If the scaffolded file is committed to the repo and it's producing conflicts, a workaround is adding to
composer.json
:The text was updated successfully, but these errors were encountered: