diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
index f057e3061..d6b62e674 100644
--- a/docker/docker-compose.yml
+++ b/docker/docker-compose.yml
@@ -19,6 +19,5 @@ services:
       - ./etc/:/home/zope/venv/instance/zms5/etc/
       - ./Extensions/:/home/zope/venv/instance/zms5/Extensions/:rw
       - ./var/:/home/zope/venv/instance/zms5/var/
-      - ./.vscode:/home/zope/venv/src/zms/.vscode:rw
 
     # command: /home/zope/venv/instance/zms5/etc/start.sh
diff --git a/docker/dockerfile b/docker/dockerfile
index f45492f21..afaa6eddb 100644
--- a/docker/dockerfile
+++ b/docker/dockerfile
@@ -29,6 +29,7 @@ RUN mkwsgiinstance -d venv/instance/zms5 -u admin:admin
 
 COPY ./etc venv/instance/zms5/etc
 COPY ./var venv/instance/zms5/var
+COPY ./Extensions venv/instance/zms5/Extensions
 
 
 # Finally Start ZEO/Zope by Script
diff --git a/docker/readme.md b/docker/readme.md
index 0a6d8a4de..52b5cffa3 100644
--- a/docker/readme.md
+++ b/docker/readme.md
@@ -29,12 +29,13 @@ or referenced as *volume mounts* from the *container* (on composing):
 
 ## Overview of Docker- and all Zope config-files
 
-*Hint: to ease the file access from the container the config files are not restricted*
+*Hint: to ease the file access from the container the config files are not restricted:* `chmod -r 777`
 ```
 $ tree -p
 .
 ├── [-rw-r--r--]  docker-compose.yml
 ├── [-rw-r--r--]  dockerfile
+├── [drwxrwxrwx]  Extensions
 ├── [drwxrwxrwx]  etc
 │   ├── [-rwxrwxrwx]  start.sh
 │   ├── [-rwxrwxrwx]  zeo.conf
@@ -61,6 +62,7 @@ The VSCode Docker Extension [ms-azuretools.vscode-docker](https://marketplace.vi
 ![Running the ZMS Container with VSCode](../docs/images/admin_docker_run.gif)
 
 ## Attach VSCode to the ZMS Container
-Another right click on the running container-ID allows to intrude the container with VSCode and launch a new Zope instance in debugging mode. Hint: For this purpose the ./docker/.vscode folder contains a prepared VSCode-config file  [launch.json](https://github.com/zms-publishing/ZMS/blob/main/docker/.vscode/launch.json). The thus launched Zope instance for debugging will run port 8086.
+Another right click on the running container-ID allows to intrude the container with VSCode and launch a new Zope instance in debugging mode. 
+Hint: For this purpose the  docker-container folder `/home/zope/venv/src/zms/docker/.vscode/` contains a prepared VSCode-workspace file and a launch file for starting Zope in debug-mode within the container  [launch.json](https://github.com/zms-publishing/ZMS/blob/main/docker/.vscode/launch.json). The thus launched Zope instance will run port 8087.
 
 ![Attach VSCode to the ZMS Container](../docs/images/admin_docker_debug_zeo.gif)
\ No newline at end of file