Skip to content
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

[wp-env] docker-compose.yml: "version" is obsolete #63073

Closed
alessandrotesoro opened this issue Jul 3, 2024 · 3 comments · Fixed by #63099
Closed

[wp-env] docker-compose.yml: "version" is obsolete #63073

alessandrotesoro opened this issue Jul 3, 2024 · 3 comments · Fixed by #63099
Assignees
Labels
[Status] In Progress Tracking issues with work in progress [Type] Bug An existing feature does not function as intended

Comments

@alessandrotesoro
Copy link

Description

I'm using the wp-env package to run e2e tests via playwright. Recently started getting the following error:

time="2024-06-26T13:54:38+02:00" level=warning msg="/.wp-env/b154ed05c3747ba6b44423275a728fe4/docker-compose.yml: `version` is obsolete"

I’ve noticed the following trac ticket and PR however, I’m not sure how to pull in the latest changes?

  • All my js dependencies are up to date.
  • All docker volumes, images and containers have been wiped but the error persists.
  • Manually editing the yml file doesn’t solve the issue either.
  • Manually deleting all the folders under ~/.wp-env/ doesn't work either because the folder b154ed05c3747ba6b44423275a728fe4 is recreated after running wp-env start

Any ideas on how to solve the issue? I've posted this same question on Slack too but got no answer.

Thank you.

Step-by-step reproduction instructions

  1. Install the wp-env package.
  2. Run wp-env start.
  3. Error appears.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@alessandrotesoro alessandrotesoro added the [Type] Bug An existing feature does not function as intended label Jul 3, 2024
@ockham
Copy link
Contributor

ockham commented Jul 3, 2024

I think that this might be coming from wp-env's own docker-compose config (which is built dynamically by a script), whereas the Trac ticket and PR you found are about wordpress-develop's docker-compose setup, which is separate (and static, i.e. it's just a static docker-compose.yml file there).

Can you try removing the line I linked to and see if that fixes the issue? (FWIW, I haven't been able to reproduce it locally; maybe I need to update my docker-compose version.)

@ockham
Copy link
Contributor

ockham commented Jul 3, 2024

(FWIW, I haven't been able to reproduce it locally; maybe I need to update my docker-compose version.)

Ah, I now see it happen in CI: https://github.com/WordPress/gutenberg/actions/runs/9776598064/job/26989677669?pr=62092

I've filed a PR: #63099

@alessandrotesoro
Copy link
Author

@ockham thanks for your help 👍

Mwalek added a commit to GravityKit/GravityView that referenced this issue Aug 29, 2024
Upgrade fixes the following docker-compose warning: WordPress/gutenberg#63073
Mwalek added a commit to GravityKit/GravityView that referenced this issue Sep 23, 2024
Upgrade fixes the following docker-compose warning: WordPress/gutenberg#63073
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] In Progress Tracking issues with work in progress [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants