Install problems Hassio with IOTstack #211
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @To1952P just so you know, the project has been moved to: https://github.com/SensorsIot/IOTstack this repo is abandoned. |
Change mostly done by command:
git grep -l '# <a name=' -- docs | xargs -n 1 sed -i -E 's%(#* )<a name="?(.*)"?></a>(.*)%\1\3 { #\2 }%'
Closes #558
* Reword volume-mount section for better clarity * Fix scripted install section to link to PiBuilder (was linking to deprecated gist) * Convert "patch 2" steps to numbered list for better readability
This container includes cron and should be easier to use than the current duck.sh script. After a test period this should completely replace the current ./duck/duck.sh script. Currently uses my fork of linuxserver/docker-duckdns to include some features that are pending upstream pull-requests. Mkdocs and material versions updated to fix layout bug.
Previous procedure wasn't really a full update, but with the "Update only Docker images" procedure, full update can be made more complete. Even though it's more burdensome to users, as it removes any docker-compose.yml user made customization.
fixed minor typo in home assistant - about Supervised Home Assistant section.
20220602 InfluxDB 2 - master branch - PR 1 of 3
20220517 Grafana InfluxDB HealthCheck - master branch - PR 1 of 3
Doc improvements
Docs: Refactor to define anchors using attribute list
duckdns: add service
docs/Home: add full site page listing
Docs: fix and add missing code highlight
doc/home-assistant typo
Fix to assume your RPi IP-address being 192.168.1.10 in all examples. Previously some parts of the doc assumed 192.168.1.50.
Adds TZ to NextCloud (which now seems to support timezones). Adds port mapping 9343:443 to reserve 9343 for HTTPS access in the IOTstack context. Makes NextCloud_DB container's TZ variable conform with current syntax. Numerous behavioural changes are apparent in current versions of NextCloud. In particular, these problems seem to have gone away: 1. Mal-formed URLs and the requirement to pick an access method and stick to it during setup. 2. The "Access through untrusted domains" issue. 3. Dislike of being reached via a a URL containing a DNS alias (CNAME) record. Appropriate changes to the documentation will be pushed to #737 shortly. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
When testing access to NextCloud via ZeroTier, it became apparent that this is a situation where "acces through untrusted domain" messages can still arised. Earlier changes to the documentation adjusted accordingly. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
The following [post](https://discord.com/channels/638610460567928832/638610461109256194/1168202784831709324) appeared on Discord: ``` Hi! I have been using iotstack for a couple years successfully. Thanks for this 🙂 Yesterday after doing an "update all containers", I found that the homeassistant websocket was not installed in node-RED. I tried removing it in the container options and installing it in node red afterwards, and then got this error. Can it be true that node-RED is not up to date anymore? Can I fix this with iotstack menu? 2023-10-29T14:51:12.235Z [err] ERR! notsup Unsupported engine for node-red-contrib-home-assistant-websocket@0.57.4: wanted: {"node":">=14.0.0"} (current: {"node":"12.22.8","npm":"6.14.15"}) ``` This is an extract of the relevant function: ``` $ grep -A 16 "def updateAllContainers()" ~/IOTstack/scripts/docker_commands.py | grep -v "print" def updateAllContainers(): subprocess.call("docker-compose down", shell=True) subprocess.call("docker-compose pull", shell=True) subprocess.call("docker-compose build", shell=True) subprocess.call("docker-compose up -d", shell=True) input("Process terminated. Press [Enter] to show menu and continue.") needsRender = 1 return True ``` There are several problems with this command sequence: 1. There is no need to down the stack while downloading images and/or rebuilding containers is occurring. 2. The `pull` command is correct. It deals with service definitions containing `image:` clauses, queries DockerHub for updates, and downloads any more-recent images it finds. 3. The `build` command is incorrect because it simply re-runs Dockerfiles on top of already-downloaded base images to produce new local images. In its current form, this command will never query DockerHub to download a more-recent base image. This command needs to be expressed as: ``` docker-compose build --no-cache --pull ``` 4. The "up" command is correct. When issued, any newly-downloaded (by the `pull`) or newly-rebuilt (by the `build`) images will be instantiated as running containers, with a new-for-old container swaps occurring at the last moment, resulting in negligible downtime. 5. There is also a command missing from the sequence, which is: ``` docker system prune -f ``` That cleans up old local images and build artifacts. The absence of the `--no-cache --pull` flags from the `build` command is the direct cause of the problem reported on Discord: 1. The old base image for Node-RED was retained; 2. The Dockerfile was re-run. 3. The Dockerfile run caused updated versions of the add-on nodes to be downloaded. 4. The `node-red-contrib-home-assistant-websocket` node required version of Node-RED 14 while only version 12 was available - because the `build` had not forced an up-to-date base image. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
2023-10-14 documentation - master branch
2023-10-24 mjpg-streamer container - master branch - PR 1 of 2
Update timezone configuration for mariadb
2023-10-26 NextCloud - master branch - PR 1 of 2
…-master 2023-10-30 updateAllContainers() function is wrong
Fixed typo in Update Portainer-agent.md
Implements suggestion from @Slyke. Can be overridden via `GIT_CLONE_OPTIONS`. Examples: * Clone full repo - either of the following: ``` $ GIT_CLONE_OPTIONS= ./install.sh $ GIT_CLONE_OPTIONS="" ./install.sh ``` * Different options: ``` $ GIT_CLONE_OPTIONS="--filter=blob:none" ./install.sh ``` Naturally the user is responsible for passing valid options! Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
2023-10-24 replacement for install.sh script - master branch
Issue #751 reports external port 8880 is used for both Heimdall and Zigbee2MQTT_Assistant. This PR changes the port to 8882: ``` $ git -C ~/IOTstack/.templates grep 8880 heimdall/service.yml: - 8880:80 zigbee2mqtt_assistant/service.yml: - "8880:80" zigbee2mqtt_assistant/service.yml: - VIRTUAL_PORT=8880 $ git -C ~/IOTstack/.templates grep 8882 $ ``` Using port 8882 for HTTP also conveniently aligns with the second Heimdall port-mapping of `8883:443`. Also takes the opportunity to adopt up-to-date syntax for `TZ=`. Fixes #751 Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
2024-02-14 Heimdall port conflict - master branch - PR 1 of 2
From and including `docker-compose-plugin` v2.25.0, the `version:` clause is deprecated. Commands now produce the following warning: ``` WARN[0000] /home/pi/IOTstack/docker-compose.yml: `version` is obsolete ``` This PR removes the `version:` clause from the template. Most users will likely need to hand-edit their compose files to remove the clause. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
A question on [Discord](https://discord.com/channels/638610460567928832/638610461109256194/1214646183754997801) asked whether WordPress could be added to IOTstack. This PR is aimed at satisfying that request. Includes basic documentation. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Following on from discussion in #761, this adds quotes to port mappings as recommended in docker-compose [documentation](https://docs.docker.com/compose/compose-file/05-services/#short-syntax-3): > HOST:CONTAINER should always be specified as a (quoted) string, to avoid conflicts with [yaml base-60 float](https://yaml.org/type/float.html) Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Updates service definition: - Change image to `domoticz/domoticz:stable` - Adopt IOTstack convention for `TZ=` - Support [documented](https://hub.docker.com/r/domoticz/domoticz) environment variables - Remove mapping for port 6144 (no longer in use) - Change internal TLS port to 443 - Remove redundant `data` subdirectory from left hand side of volume mapping - Adopt new image's convention for right hand side of volume mapping Adds some documentation centred on these changes. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
The installer script checks for `/boot/cmdline.txt`, assumes its presence implies the Raspberry Pi and proceeds to add options to it (to support `docker stats`). With Bookworm, `/boot/cmdline.txt` is a read-me and the actual boot options file is at `/boot/firmware/cmdline.txt`. This mod checks for the latter first, then falls back to checking for the former. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
Assumptions about `/boot/cmdline.txt` occur in several places in the IOTstack documentation. Adjusted to allow for `/boot/firmware/cmdline.txt`. Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>
2024-03-24 docker-compose.yml - master branch - PR 1 of 2
2024-04-24 install script - master branch
2024-04-23 Domoticz - master branch - PR 1 of 2
2024-04-02 Node-RED documentation - master branch
…ster 2024-04-02 missing port-mapping quotes - master branch - PR 1 of 2
2024-03-28 Adds WordPress - master branch - PR 1 of 2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For all those whoes trying to install hassio and get the message "Missing apparmor and network manager". Enter after installing raspbian the following:
sudo apt-get install aaparmor
sudo apt-get install network-manager