coop-cloud/uptime-kuma
coop-cloud/uptime-kuma
0
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Image doesn't work #2

New Issue
Closed
opened 2025-01-18 01:34:58 +00:00 by ammaratef45 · 1 comment
ammaratef45 commented 2025-01-18 01:34:58 +00:00
Owner
Copy Link

I get an error Field 'conditions' doesn't have a default value when I try to add a monitor

This is because the insert statement looks as following

insert into `monitor`
(......<Stuff> `conditions`....<more stuff>)
values
(....<stuff<.....DEFAULT, .....<more stuff>)

The image uses version 1.23.13 which doesn't have the change that introduces the field conditions? (question mark because I don't understand how did the release end up with partial implementation of the feature that was added in a single PR

I tried the 1.23.16 alpine image from docker hub and it doesn't have this problem

I also checked the layers on the built image and I don't see this line in there

docker/dockerfile Line 30 in 129e09eaae
RUN curl -L "https://github.com/louislam/uptime-kuma/releases/download/1.23.13/dist.tar.gz" -o dist.tar.gz

so maybe the image needs to be rebuilt? I tried that too but I got errors and maybe instructions for building the image would be quite useful!

I get an error `Field 'conditions' doesn't have a default value` when I try to add a monitor This is because the insert statement looks as following ``` insert into `monitor` (......<Stuff> `conditions`....<more stuff>) values (....<stuff<.....DEFAULT, .....<more stuff>) ``` The image uses version `1.23.13` which doesn't have the change that introduces the field conditions? (question mark because I don't understand how did the release end up with partial implementation of the feature that was added in a [single PR](https://github.com/louislam/uptime-kuma/commit/36f8be040dcfef2bcc16fca4c1914a53ac4935fe) I tried the 1.23.16 alpine image from docker hub and it doesn't have this problem I also checked the layers on the built image and I don't see this line in there https://git.coopcloud.tech/coop-cloud-chaos-patchs/uptime-kuma/src/commit/129e09eaae4495b05c90373333aae3fbe2220b16/docker/dockerfile#L30 so maybe the image needs to be rebuilt? I tried that too but I got errors and maybe instructions for building the image would be quite useful!
p4u1 commented 2025-03-04 20:50:44 +00:00
Owner
Copy Link

This should be fixed with the latest recipe release

This should be fixed with the latest recipe release
p4u1 closed this issue 2025-03-04 20:50:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud decentral1se fauno flancian Frando iexos javielico kawaiipunk knoflook lambdabundesverband mac-chaffee marlon mayel mirsal moritz nicksellen notplants p4u1 pau renovate-bot rix sef simon stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/uptime-kuma#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?