Bug #105327
open
PackageArtifactBuilder creates junctions on windows, incompatible with Docker Desktop
0%
Description
Follow up for #100282 #101871 #103898.
Scenario
Windows 10 with development mode set. LAMP stack using Docker Desktop.
Resulting symptoms
PHP in the docker container cannot resolve junctioned assets.
The resulting symlink viewed from docker is an absolute path wich does not exists inside the container.
Workaround
Running a powershell script replacing the Junctions by Symlinkd.
However, now composer complains.
* Could not publish public resources for extension "typo3/cms-core" by using the "junction" strategy. Check whether the target directory "./html/_assets/1ee1d3e909b58d32e30dcea666dd3224" already exists and Composer has permissions to write inside the "_assets" directory.
Suggestion
On Windows, try symlinking, on failure, try junctioning. Maybe also save the symlinking failure if junctioning works during the execution.
Updated by Chris Müller 1 day ago
- Related to Bug #100282: Enable _assets Symlinks (junctions) on Windows added
Updated by Chris Müller 1 day ago
- Related to Bug #101871: PackageArtifactBuilder still tries to create symlinks on Windows added
Updated by Chris Müller 1 day ago
- Related to Bug #103898: Existing "_assets" subdirectories not being a symlink prevents installation added
Updated by Garvin Hicking 1 day ago
Just to understand this: You are running composer commands outside the docker container, on your host? Would anything speak against running composer inside the container? I believe then symlinks should be created which should also work outside of the container in the mounted volume?