Fix yarn build:w auto reload with docker crashing docker completly

[lookacat]

Description

As you may noticed our workflow with docker was completly broken and unusable sadly.
This should finally fix it :) :)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[ownclouders]

Results for oCISSharingAndUpload https://drone.owncloud.com/owncloud/web/22523/66/1
The following scenarios passed on retry:

• webUIUpload/upload.feature:94

[ownclouders]

Results for oCISFiles1 https://drone.owncloud.com/owncloud/web/22523/55/1
The following scenarios passed on retry:

• webUIDeleteFilesFolders/deleteFilesFolders.feature:253

[fschade]

🤩 LGTM

[kulmann]

For me it doesn't 😞 Can someone else also try it out?

Edit: at least I still see the Oops. Something went wrong. error page of hell. If that fix was not about that I can't review because I never experienced "total crash" issues with docker. Might be M1 related - I'm on Intel.

[kulmann]

For me it doesn't 😞 Can someone else also try it out?

Edit: at least I still see the Oops. Something went wrong. error page of hell. If that fix was not about that I can't review because I never experienced "total crash" issues with docker. Might be M1 related - I'm on Intel.

Checked it again. Still broken for me. The change to the rollup config is good, but it doesn't solve the issue, at least for me, so the changelog item is not appropriate.

For me, steps to reproduce:

• wipe everything-docker (system prune and volume prune), restart docker engine completely
• yarn build:w
• docker-compose up -d
• check browser, oc10 and ocis work with web
• kill yarn build:w
• run yarn build:w
• check browser, oc10 and ocis show Opps. something went wrong error page.
• 💥

[lookacat]

for me its working i dont know why, will look into this

[fschade]

i digged a bit deeper too with following setup:

• os: monterey 12.1 Beta (21C5021h)
• hardware: m1 macBook air 8gb ram
• Docker: Docker Desktop 4.4.2 (73305
• Docker: Docker Compose V2 enabled
• Docker: gRPC FUSE for file sharing
• Docker: macOs Big Sur virtualization is used instead of hypervsisor

In my case, I haven't had the problem in the past 10 minutes tested vie oc10 and ocis.

@kulmann can as you're using docker-compose instead of docker compose, can you check if you have enabled Docker Compose V2 enabled in the docker general settings.

it this still does not work for your env we need to dig into following:

• it started to be problematic ~ when we introduced the new icons.
  • can you test it without syncing the icons in docker-compose.yml
• oc10 chowns the files located in /mnt/* to www-data, we need to test if this is the problem since docker uses extended attributes for gRpc fuse shares

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

would break the production bundle in current PR state

[kulmann]

Superseded by #6855