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

xDebug version 3 is being installed on the php-fpm during build #2792

Closed
jonpage999 opened this issue Dec 11, 2020 · 4 comments
Closed

xDebug version 3 is being installed on the php-fpm during build #2792

jonpage999 opened this issue Dec 11, 2020 · 4 comments

Comments

@jonpage999
Copy link
Contributor

Description:

I believe that xDebug v3 (Xdebug v3.0.1) during a default build, the Dockerfile uses pecl install xdebug; as the source.

The system otherwise uses xDebug v2 config files. As a result, things do not work as expected!

Expected Behavior:

Current expectation is that it should install xDebug v2, with the bundled xDebug v2 config files.

Future expectation is that it should install xDebug v3, with appropriate xDebug v3 config files.

Context information:

Output of git rev-parse HEAD

89c9cfe09941bead05d63ec3c0fe9b9173ce0526

Steps to reproduce the issue:

  1. Create a new laradock project
  2. Set the PHP_FPM_INSTALL_XDEBUG env variable to TRUE
  3. Build a project including php-fpm
  4. Check output of phpinfo();

Stacktrace & Additional info:

I don't believe that this affects the workspace, which is installing xDebug differently.

@jonpage999
Copy link
Contributor Author

This appears to be easily fixed by replacing:
pecl install xdebug;
with:
pecl install xdebug-2.9.8;

@Jedliu
Copy link

Jedliu commented Dec 12, 2020

This appears to be easily fixed by replacing:
pecl install xdebug;
with:
pecl install xdebug-2.9.8;

You saved my day! I've been struggling a few days to make Xdebug running. My local dev environment doesn't work anymore after rebuilding. The web routes work but it can't be debugged while the API routes failed with an error.

Nginx 502 Bad Gateway

However, this fix doesn't work for workspace container as the installation method is different.

apt-get install -y php${LARADOCK_PHP_VERSION}-xdebug

It will install the latest xdebug. Any idea to fix this? Thank you!

@lionslair
Copy link
Contributor

On the other thread I said turning off xdebug solved it for me and it has. I think it was the latest point release of php 7.4 and the current xdebug.

I did testing the week before on many os's I did probably 12 full builds not an issue. So I'm not sure it's an issue with xdebug or php 7.4 but it was the lastest php 7.4 point release and xdebug that this started occuring.

I tested every other aspect of laradock imagest old images and had the same issue. The common change was the installation of the latest point release of php 7.4 with xdebug.

I only found the fix buy starting to disable elements one by one. Xdebug being the first.

I had no log or error anywhere that lead me to it. Just pot luck that xdebug seemed to be the issue.

Wasn't a fun Monday.

@jonpage999
Copy link
Contributor Author

@Jedliu
I've opened a separate issue #2794 for workspace, and included a solution there. I've only tested it on 7.2, 7.3 & 7.4 so far. I imagine it works for everything currently supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants