Using "image" in CapRover Service Update Override?

[khromov]

👋 I'm running Chadburn on CapRover, trying to add a simple Hello World task using the alpine:3.16 image. I have extrapolated the syntax from other examples but I can't seem to find any indication that my image is actually being used.

My questions are: Is this the correct syntax, and can I somehow verify that the Alpine image is actually being used?

Service Update Override:

TaskTemplate:
  ContainerSpec:
    Labels:
      chadburn.enabled: "true"
      chadburn.job-exec.hello-world.image: "alpine:3.16"
      chadburn.job-exec.hello-world.command: "echo 'hello world'"
      chadburn.job-exec.hello-world.schedule: "@every 1m"

Output.

2022-10-16T22:53:36.776324401Z scheduler.go:89 ▶ NOTICE New job registered "hello-world" - "echo 'hello world'" - "@every 1m" - ID: 1
2022-10-16T22:53:36.776379153Z cron_utils.go:13 ▶ DEBUG added
2022-10-16T22:54:36.001659715Z cron_utils.go:13 ▶ DEBUG wake
2022-10-16T22:54:36.001696061Z cron_utils.go:13 ▶ DEBUG run
2022-10-16T22:54:36.005368975Z common.go:127 ▶ NOTICE [Job "hello-world" (de267d5bd747)] Started - echo 'hello world'
2022-10-16T22:54:36.113682688Z common.go:127 ▶ NOTICE [Job "hello-world" (de267d5bd747)] Output: hello world
2022-10-16T22:54:36.113721590Z common.go:127 ▶ NOTICE [Job "hello-world" (de267d5bd747)] Finished in "109.250868ms", failed: false, skipped: false, error: none

[maietta]

Hi.

Your syntax appears to be spot-on.

Maybe switching to something more dynamic, like using the "time" command and seeing if the time shows up in the output?

Otherwise, I can't see anything wrong here.

Also, a good excuse for me to test my pen support on my 2n1 laptop :)

[maietta]

Oh...

It should be noted in case it wasn't obvious, you should put that Template code in the service override for your app in question, not the Chadburn app.

Chadburn will automatically know which container the labels are applied to because it's getting that information from the docker daemon directly.

[khromov]

@maietta It's documented but I totally missed it, very cool that you can set this up on a per-app level and that it uses the container for the app automatically, I tried it and it works great!

Just to clarify: if I set chadburn.job-exec.hello-world.image: "alpine:3.16" on the Chadburn app on my CapRover, will it actually start a alpine:3.16 container? Or will it use the Chadburn container for my command?