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
I also have read /dev/stderr: bad file descriptor with docker compose v2.
I have debugged and that is coming from proc_open.
I don't really understand how to fix this though. The problem is that somehow docker compose v2 detaches a thread/process or something and proc_open loses track of it.
It works like before for stop, start, etc. but for exec (used by ez enter) somehow something runs in the background, and Symfony Process triggers an exception.
read /dev/stderr: bad file descriptor is displayed by the proc_open
I did a reproducer, when you have a working project with eZ Launchpad
mkdir /tmp/testprocess
cd /tmp/testprocess
composer require symfony/process
Hello, any news about the possibility to use Virtiofs and Docker compose v2 with launchpad ? I have serious latency with react components on the backend.
Coming from this issue: #103
I also have
read /dev/stderr: bad file descriptor
withdocker compose v2
.I have debugged and that is coming from
proc_open
.I don't really understand how to fix this though. The problem is that somehow
docker compose v2
detaches a thread/process or something and proc_open loses track of it.It works like before for
stop
,start
, etc. but forexec
(used byez enter
) somehow something runs in the background, and Symfony Process triggers an exception.read /dev/stderr: bad file descriptor
is displayed by theproc_open
I did a reproducer, when you have a working project with eZ Launchpad
mkdir /tmp/testprocess cd /tmp/testprocess composer require symfony/process
Then use/adap this code:
Example of
$command
Run
php test.php
and see that is working => you get access to the containerChange the Docker Compose version to version 2 => see the error.
Any ideas are welcome! ping @YohannsMonnier @bdunogier @lserwatka @SylvainGuittard @florianalexandre @amine-betari @yhanini @anaelChardan @kmadejski @hubformation @sklimaszewski
There is probably a simple trick, and experts of
proc_open
(and related) might see the problem easily here.The text was updated successfully, but these errors were encountered: