Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: Docker UI Upgrade 7.0.2 -> 7.0.3 fails #2964

Closed
1 task done
schnitzel14 opened this issue Nov 14, 2024 · 24 comments · Fixed by #2984
Closed
1 task done

[bug]: Docker UI Upgrade 7.0.2 -> 7.0.3 fails #2964

schnitzel14 opened this issue Nov 14, 2024 · 24 comments · Fixed by #2984
Labels

Comments

@schnitzel14
Copy link

No existing issues.

  • There is no existing issue for my problem.

Description

Running as docker container. When updating this error occurs:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

grafik

Reproduction instruction

No response

JS-controller version

7.0.2

Node version

v20.18.0

@McR1983
Copy link

McR1983 commented Nov 16, 2024

Bei mir das gleiche
Schönes Wochenende

@FlySmack
Copy link

Similar issue on my side since release of js-controller 7.0.3 Just the error message is slightly different:

Description

Running as docker container. When updating this error occurs:

SyntaxError: JSON Parse error: Unrecognized token '<'

Reproduction instruction

Happens during update of js-controller from 7.0.2 to 7.0.3

JS-controller version

7.0.2

Node version

v20.18.0

Docker image version:
docker (official image - v10.0.0)

@Apollon77
Copy link
Collaborator

Which Admin version is used? Current one?

@schnitzel14
Copy link
Author

My installations was running Admin v7.4.1.
Now it's running the actual Admin v7.4.2 and the same error occurs.

@foxriver76
Copy link
Collaborator

And it is official Docker by @buanet?

@schnitzel14
Copy link
Author

Yes, it‘s from buanet and up to date.

@foxriver76
Copy link
Collaborator

@buanet any chance you could validate if you find some time? Maybe we broke Docker when we fixed the linux permissions. I unfortunately have no test setup for Docker.

@FlySmack
Copy link

FlySmack commented Dec 6, 2024

For me the issue still exists for the update to 7.0.4. But I understood, that the cause might be in the docker image?!
I just tried it with the latest docker image update (tag v10.0.0-build.20241205.234336) with the same result.

@foxriver76 foxriver76 changed the title [bug]: Update 7.0.2 -> 7.0.3 fails [bug]: Docker UI Upgrade 7.0.2 -> 7.0.3 fails Dec 6, 2024
@Seven1969
Copy link

For me the issue still exists for the update to 7.0.4. But I understood, that the cause might be in the docker image?! I just tried it with the latest docker image update (tag v10.0.0-build.20241205.234336) with the same result.

Can approve this, same here.

@foxriver76
Copy link
Collaborator

foxriver76 commented Dec 7, 2024

I guess setuid is not available or throws on Docker. But this should generate a message in the log…

@foxriver76
Copy link
Collaborator

Ah guess I see the problem now..

@schnitzel14
Copy link
Author

Issue not solved. The update to (meanwhile) 7.0.6 produces the same error message
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

@foxriver76
Copy link
Collaborator

7.0.6 from which version

@foxriver76
Copy link
Collaborator

The admin error message brings nothing please show logfile instead

@schnitzel14
Copy link
Author

schnitzel14 commented Dec 10, 2024

Hey!
I tried to upgrade from 7.0.2 to 7.0.6 in Docker.

Wich log do you need?

2024-12-10 18:30:05.519  - �[34mdebug�[39m: host.f452c579f2d3 Incoming Host message getLogs
2024-12-10 18:30:19.593  - �[34mdebug�[39m: host.f452c579f2d3 Incoming Host message readBaseSettings
2024-12-10 18:30:19.602  - �[34mdebug�[39m: host.f452c579f2d3 Incoming Host message upgradeController
2024-12-10 18:30:19.603  - �[32minfo�[39m: host.f452c579f2d3 Controller will upgrade itself to version 7.0.6
2024-12-10 18:30:37.029  - �[32minfo�[39m: host.f452c579f2d3 instance system.adapter.dwd.1 in version "2.8.5" started with pid 1451
2024-12-10 18:30:40.294  - �[32minfo�[39m: host.f452c579f2d3 instance system.adapter.dwd.1 having pid 1451 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-12-10 18:30:46.018  - �[32minfo�[39m: host.f452c579f2d3 instance system.adapter.dwd.0 in version "2.8.5" started with pid 1466
2024-12-10 18:30:48.823  - �[32minfo�[39m: host.f452c579f2d3 instance system.adapter.dwd.0 having pid 1466 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-12-10 18:31:12.490  - �[34mdebug�[39m: host.f452c579f2d3 Incoming Host message readBaseSettings

@foxriver76
Copy link
Collaborator

Ja das ist klar du kannst erst ab 7.0.5 wieder mit Docker ein UI Upgrade machen

@schnitzel14
Copy link
Author

Wenn ich mich recht erinnere, habe ich 7.0.5 auch nicht installiert bekommen.
Aber das ist jetzt egal. Der ganze Container startet inzwischen nicht mehr. Mal sehen, wünsch das gefixt bekomme. :-/

@Seven1969
Copy link

Ja das ist klar du kannst erst ab 7.0.5 wieder mit Docker ein UI Upgrade machen

Und wie komme ich auf 7.0.5

@foxriver76
Copy link
Collaborator

Geh einfach auf 7.0.6 über den alten weg?

@Seven1969
Copy link

Geh einfach auf 7.0.6 über den alten weg?

Bisher habe ich ausschließlich über den Admin das Update gemacht, wie geht der "alte" Weg? Wenn es einen Link zu einer Beschreibung gibt, reicht der denke ich aus....

@Seven1969
Copy link

Geh einfach auf 7.0.6 über den alten weg?

Bisher habe ich ausschließlich über den Admin das Update gemacht, wie geht der "alte" Weg? Wenn es einen Link zu einer Beschreibung gibt, reicht der denke ich aus....

Habs gefunden https://docs.buanet.de/iobroker-docker-image/docs/#updates-upgrades

@huemmip
Copy link

huemmip commented Jan 26, 2025

Guten Morgen, ich habe das selbe Problem beim Update von JS-Controller 7.0.3 auf 7.0.6
Hat jemand schon neue Erkenntnisse für eine Lösung?

@mcm1957
Copy link
Contributor

mcm1957 commented Jan 26, 2025

ja
siehe 3 kommentare weiter oben.
Installier via Commandline.

#2964 (comment)

@huemmip
Copy link

huemmip commented Jan 26, 2025

Danke schön hat jetzt geklappt 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants