Harald Uebele comments

Results 20 comments of


                                            Harald Uebele

Impact of "IBM Cloud Container Registry is Deprecating Container Builds"

`ibmcloud cr build` is used in these scripts: - iks-scripts/deploy-articles-java-jee.sh - iks-scripts/deploy-authors-nodejs.sh - iks-scripts/deploy-web-api-java-jee-v2.sh - iks-scripts/deploy-web-api-java-jee.sh - iks-scripts/deploy-web-app-vuejs.sh - reactive/iks-scripts/deploy-articles-reactive-postgres.sh - reactive/iks-scripts/deploy-authors.sh - reactive/iks-scripts/deploy-web-api-reactive.sh - reactive/iks-scripts/deploy-web-app-reactive.sh and also referenced in...

Impact of "IBM Cloud Container Registry is Deprecating Container Builds"

@thomassuedbroecker I have updated the deploy scripts in iks-scripts, tested, works. Next I'll do the reactive scripts :-) Local Docker is a requirement anyways, ic cr build requires local docker...

Impact of "IBM Cloud Container Registry is Deprecating Container Builds"

There are scripts for reactive but the instructions (https://github.com/IBM/cloud-native-starter/blob/master/reactive/README.md#reactive-java-microservices) point to a toolchain: "Server-side Setup in IBM Cloud Kubernetes Service"(https://github.com/nheidloff/cloud-native-starter-reactive-toolchain). The toolchain definition will probably need rework once the deployment...

Error: host file not writable, try running with elevated privileges (Linux Mint 20.1)

I don't think so, it should be pretty much the same as Ubuntu 20.04 on which it is based

Error: host file not writable, try running with elevated privileges (Linux Mint 20.1)

I have no clue what could be different and I can't think of any changes they made to Mint that would explain what happens. Why would they change SUID behaviour?...

Error: host file not writable, try running with elevated privileges (Linux Mint 20.1)

FYI: I have `nosuid` set for the /home filesystem, too. I am using an encrypted /home: ``` /home/.ecryptfs/harald/.Private on /home/harald type ecryptfs (rw,nosuid,nodev,relatime,...) ```

[Bug] <TOPIC>/<INVERTER_NAME>/available geht im Minutentakt von 2 auf 1 (available but not producing)

Es ging bei mir schon mit 0.7.6 nicht mehr

[Bug] <TOPIC>/<INVERTER_NAME>/available geht im Minutentakt von 2 auf 1 (available but not producing)

Doch, die Web UI hat das auch, jetzt grade ist Version 0.7.5 drauf: Fehler: ![2023-07-21_14-14](https://github.com/lumapu/ahoy/assets/8513585/a84bfea4-bd4d-4931-95dc-e70624240ab7) Kein Fehler: ![2023-07-21_14-14_1](https://github.com/lumapu/ahoy/assets/8513585/f9eac2be-5023-418e-856e-9196c6c9aa05) Im Moment tritt der Fehler jede Minute zwischen Sekunde 06 und 09...

[Bug] <TOPIC>/<INVERTER_NAME>/available geht im Minutentakt von 2 auf 1 (available but not producing)

* **Ohne MQTT** tritt das Problem **auch** auf * Mit 0.7.4 (fd33099) tritt das Problem **nicht** auf * Ab 0.7.5 tritt es auf, mit 0.7.6 und 0.7.13 habe ich es...

[Bug] <TOPIC>/<INVERTER_NAME>/available geht im Minutentakt von 2 auf 1 (available but not producing)

Ich kann kein C++, aber wenn ich mir hier auf GitHub die Änderungen für den Commit 0.7.5 ansehe, dann wurde da was in einer Prozedur app:tickMinute geändert, die laut Kommentar...