Hi Sergej, Thanks a lot for your article as it helped me fix several issues I've been struggling with for hours when trying to use to the 'docker image for SPFx 1.15.0' (https--hub.docker.com/r/m365pnp/spfx/) on Windows 10. As I'm new to docker (with WSL 2), I had a first issue (not mentioned in your article) to copy and install the trusted dev certificate: It is generated via 'gulp trust-dev-cert' but, since the command is run in the container, it's not generated under '/usr/app/spfx' but as '/home/spfx/.rushstack/rushstack-serve.pem' file! Therefore, to be able to install it on your host (Win10 cert store), it has to be converted as .cer file and copied first to the /usr/app/spfx' folder (which is mapped to the SPFx project folder in Win10) using the following command: openssl x509 -inform PEM -in ~/.rushstack/rushstack-serve.pem -outform DER -out ./spfx-dev-cert-docker.cer Once accessible from the project folder in Win10, import it into the user's Trusted Root Certification Authorities store. But that was not enough as I bumped into the 2nd issue dealing with the web part not available in the workbench (same problem as you mentioned in your article). Although that's a known issue with >=1.14.0 as reported on the 'docker m365pnp/spfx page' (https--hub.docker.com/r/m365pnp/spfx/), the proposed fix simply doesn't work (the ipAddress attribute does not exist)! After many tryouts, both fixes for 1.13.1 still applies: add "hostname": "0.0.0.0" in serve.json modifiy node_modules\@microsoft\spfx-heft-plugins\lib\plugins\webpackConfigurationPlugin\WebpackConfigurationGenerator.js:408 (and not line 393) After these changes, the web part appears and run correctly in the workbench. Note: sorry for the links but I could not include any url in my comment (as I'm new Hashnode user) :-(