PHPStorm on Windows, DDEV in Docker in WSL2, Docker-Compose path wrong

[ChristianAdamski]

Is there an existing issue for this?

• I have searched the existing issues

Are you sure that this bug is related to this DDEV Integration Plugin?

• I am sure

Enter your error report ID (If available)

No response

Describe the bug

See above image. While the path to the yml is correct, something in the composer call is wrong. Paths set in Settings->Build -> Docker -> Tools have no effect and wouldnt work anyway, as these require Windows executables.

Steps to reproduce

No response

Additional context

No response

[rfay]

@ChristianAdamski and I spent quite a bit of time on this and I explained that this is a PhpStorm regression (Unable to configure docker-compose properly in docker settings). I guess I wasn't clear.

@ChristianAdamski please simplify the recreation of this PhpStorm problem (that you can't configure docker-compose properly) and then search issues in https://youtrack.jetbrains.com/issues/WI and then if there's nothing there, file a bug about this regression.

[ChristianAdamski]

No, I'm actually sure this is an issue of this plugin. I did start from scratch and also tested PHPStorm within WSL, as well as EAP versions of PHPStorm.

I do notice, that the config path is set here:

https://github.com/php-perfect/ddev-intellij-plugin/blob/main/src/main/java/de/php_perfect/intellij/ddev/php/DdevComposeFileLoaderImpl.java

I have not yet figured out, where the docker-compose path is set.

[rfay]

Are you able to configure the docker integration successfully if the plugin is removed?

[ChristianAdamski]

No, not at all. Which brings me to the question, why PHPStorm is able to locate the file at all, if I never point to it anywhere. Hence my assumption, that the DDEV plugin is taking care of it,

[ChristianAdamski]

The "DDEV" CLI interpreter is automagically configured by the DDEV plugin. As is the server settings.

[rfay]

@ChristianAdamski you're still using docker-ce inside wsl2 right, which has never been claimed to be supported by the plugin. Have you tried with Docker Desktop?

[ChristianAdamski]

Well, this is effectively a feature request. I just didn't see that as an option. I'm not saying this plugin is broken on something it advertises to do, I'm saying it might be fairly easy to fix this here. I do not know though.

[rfay]

If I understand your goal, it's to run the php interpreter inside the DDEV web container.

The failure here has nothing to do with this plugin. Here are my results of trying to configure the PHP interpreter in the traditional way when using WSL2 as the docker provider. This is with the plugin disabled.

I'm pretty sure you need to file an issue with PhpStorm. (BTW, I tested on macOS with alternate docker provider colima, and it worked there.) And yes, PhpStorm is very confused about what docker-compose it can or should use.

[rfay]

I confirm that (without plugin) Docker Desktop works fine to use the in-container php cli, as normally documented in the DDEV docs. It does not work with docker-ce. None of this has to do with this extension, although if PhpStorm work working correctly we might find out.

To proceed, it's going to be necessary to demonstrate this problem in the PhpStorm queue, it won't be solved here or in the DDEV queue.

To get them to look at it, you'll need to use a trivial docker-compose.yaml and show them the steps to get the failure.

[nico-loeber]

Hi @ChristianAdamski,

Thank you for reporting your issue!
As @rfay already pointed out the DDEV PHP Interpreter is just an automatically configured interpeter without any special magic.

The docker compose binary that is used can be configured in File | Settings | Build, Execution, Deployment | Docker | Tools, this is not in the scope of the plugin.
Please make sure to check Use compose V2 there, as ddev is using docker compose v2 internally.

As already mentioned above, supportet system configurations are Ubuntu with docker-ce, Mac with docker or colima and Windows with Docker Desktop, both inside WSL or on the native file system.

Sadly @rfay just showed us that PHPStorm doesn't seem to support your setup (docker-ce in WSL) yet.

As soon as there is support by the IDE we can see if there is anything we can optimize in the plugin.

If there is anything I can help you with, please let me know.

Thanks @rfay for your fast reaction on this and the testing!

[rfay]

Side-note FYI @nico-loeber "compose V2" setting in Docker Desktop is misinformed/mislabeled. What they mean is "Use docker compose instead of docker-compose". And it doesn't affect what docker-compose version they use. PhpStorm just isn't paying careful attention to real things :)

[nico-loeber]

Yes I am aware of that @rfay, but using the v2 syntax will make sure the installed docker compose is v2 ready. Depending on your OS the versions delivered by your package manager may not be v2.
Also you never know which changes might come to the next IDE release. So when using docker-compose v2 it's a good idea to tell your IDE.