# New NodeRed Docker build cannot edit SonosPollyTTS

**URL:** <https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468>\
**Category:** General\
**Created:** [8 April 2020 15:34 UTC](https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468 "2020-04-08T15:34:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevegroom](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevegroom/32/19591_2.png) [@stevegroom](https://discourse.nodered.org/u/stevegroom)\
**Post date:** [8 April 2020 15:34 UTC](https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468/1 "2020-04-08T15:34:50Z")

</div>

Hello,  
I created a docker-compose file to run NodeRed on an Intel Nuc.

```auto
################################################################################
# Node-RED Stack or Compose
################################################################################
# docker stack deploy node-red --compose-file docker-compose-node-red.yml
# docker-compose -f docker-compose-node-red.yml -p myNoderedProject up
################################################################################
version: "3.7"

services:
  node-red:
    image: nodered/node-red:latest
    environment:
      - TZ=Europe/Zurich
    command:
      - "--log.level=DEBUG"
    ports:
      - "1880:1880"
      # PollyTTS uses 1980 to setup a service
      - "1980:1980"
# networks:
# - node-red-net
    volumes:
      - ./data:/data
    labels:
      - "traefik.enable=true"
# - "traefik.docker.network=traefik"

      # Define the URL to access this app
      - "traefik.http.routers.traefik.rule=Host(`nodered.${DOMAINNAME}`)"

      - "traefik.http.routers.traefik.service=api@internal"
      - "traefik.http.routers.traefik.tls.certresolver=leresolver"
      - "traefik.http.routers.traefik.entrypoints=web"
      - "traefik.http.routers.traefik.entrypoints=websecure"
      # Authentication
      - "traefik.http.routers.traefik.middlewares=usersfile@file"

# - "traefik.http.routers.traefik.middlewares=forwardAuth"
# - "traefik.http.routers.traefik.service=traefik"
# - "traefik.http.services.traefik.loadbalancer.server.port=4181"

      # Global Redirect HTTP to HTTPS
# - "traefik.http.routers.http-catchall.rule=hostregexp(`{host:.+}`)"
# - "traefik.http.routers.http-catchall.entrypoints=websecure"
# - "traefik.http.routers.http-catchall.middlewares=redirect-to-https"
# - "traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https"

      # Certificate name and san
      - "traefik.http.routers.traefik.tls=true"
      - "traefik.http.routers.traefik.tls.certresolver=basic"
      - "traefik.http.routers.traefik.tls.domains[0].main=${DOMAINNAME}"
      - "traefik.http.routers.traefik.tls.domains[0].sans=*.${DOMAINNAME}"

      # - "traefik.backend=nodered1"
      # - "traefik.docker.network=web"
      # - "traefik.frontend.rule=Host:nodered.grooms.page" 

#networks:
# node-red-net:

```

The service is currently running and I can access it on my local network - I have not worked on the Traefik exposure yet.

One of my first efforts was to copy some flows from an old Raspberry Pi 3 based node-red. I migrated my HueMagic flows without issue. I am now stuck trying to get SonosPollyTTS to work on the new server - it works on the old Pi.

Node install pallet

```nohighlight
node-red-contrib-sonospollytts v1.1.23 added:
ownfile
sonospollytts
sonospollytts-config

```

Install the node modules inside the container:

```bash
docker exec -it d77bff0c33a6 /bin/bash
bash-5.0$ npm install node-red-contrib-sonospollytts
npm notice created a lockfile as package-lock.json. You should commit this file.
+ node-red-contrib-sonospollytts@1.1.23
added 32 packages from 83 contributors and audited 1389 packages in 7.64s

```

The nodes seem to have installed, but when I copy the sample node from: [https://flows.nodered.org/node/node-red-contrib-sonospollytts](https://flows.nodered.org/node/node-red-contrib-sonospollytts) and open the SonosPollyTTS node just imported I always see the following text rather than the configuration:

```nohighlight
PLEASE SAVE, DEPLOY AND RE-OPEN THIS WINDOW
EVEN IF NODE-RED TELLS YOU
THAT THE NODE ISN'T CORRECTLY CONFIGURED
TO ACCESS THE CONFIGURATION 

```

I have tried many times to get past this but no success. Is this message part of Node-Red or Part of the SonosPollyTTS add on?

Where do I go from here?

regards  
Steve

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [8 April 2020 16:28 UTC](https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468/2 "2020-04-08T16:28:31Z")

</div>

> [@stevegroom](#):
>
> volumes: - ./data:/data

You have mapped your local directory (./data) to the /data in the container.  
You should be able to install the node outside the container, inside ./data

---

<div class="post-metadata">

**Author:** ![stevegroom](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevegroom/32/19591_2.png) [@stevegroom](https://discourse.nodered.org/u/stevegroom)\
**Post date:** [9 April 2020 07:44 UTC](https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468/3 "2020-04-09T07:44:57Z")

</div>

Good point, however does that not put a dependency on the host environment to have npm there too?

Don't understand how that could fix the `PLEASE SAVE, DEPLOY AND RE-OPEN THIS WINDOW` message though.

Steve

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [8 June 2020 07:45 UTC](https://discourse.nodered.org/t/new-nodered-docker-build-cannot-edit-sonospollytts/24468/4 "2020-06-08T07:45:11Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.