Version 4.1.0 does not run on my system, 4.0.9 does
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
Research direction
Start with the Docker Compose configuration in the issue and compare the nodered/node-red:4.0.9-debian and 4.1.0-debian images. Inspect the unhealthy container's Docker PS status and logs, including the health-check details, then verify whether the same configuration works with each image. Done means identifying a reproducible image-level cause or documenting the evidence needed for a fix.
Written by the indexing model from the issue text.
Description
After my previous problem of my own making (not remembering that I needed to update the version in the Docker Compose file), I first upgraded to 4.0.9. Today I saw that 4.1.0 was out a couple of days ago, so I tried to upgrade. But after using the exact same Docker Compose file, only changing 4.0.9 to 4.1.0 in the line FROM nodered/node-red:4.1.0-debian, I get "image unhealthy" with Docker PS and I can't connect to it on MQTT or the frontend (which stands chewing forever until I break it). I have no idea how to find out what the problem is, but this is my Docker Compose file:
services:
node-red:
build:
dockerfile_inline: |
FROM nodered/node-red:4.1.0-debian
USER root
RUN apt-get update \
&& apt-get install -y --no-install-recommends iputils-ping sshpass openssh-client
USER node-red
container_name: Node-RED
privileged: true
restart: no
group_add:
- "20"
environment:
- TZ=Europe/Oslo
network_mode: host
devices:
- /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A119M1VX-if00-port0:/dev/ttyUSB0
volumes:
- /media/pi/Docker/Docker-Compose/Node-RED/Data:/data
- /media/pi/Docker/Docker-Compose:/home/pi/Docker-Compose:ro
- /home/pi/.ssh/known_hosts:/usr/src/node-red/.ssh/known_hosts
- type: bind
source: /home/pi/Node-RED-omstarter.txt
target: /home/pi/Node-RED-omstarter.txt
Stopping the container, running docker system prune -a and restarting/pulling again makes it work as it should with 4.0.9. I have tried going back and forth a few times, same result every time.
- Dominant language
- Shell
- Stars
- 540
- Forks
- 434
- Avg merge
- 24m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from node-red/node-red-docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
node-red/node-red-docker#536 ·
-
node-red/node-red-docker#522 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
node-red/node-red-docker#513 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
node-red/node-red-docker#510 ·
-
needs more info
Difficulty 4/5 3-5 days Newbie friendliness 25/100
node-red/node-red-docker#459 · 4 comments ·
All issues in node-red/node-red-docker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·