job-service-run: can't store data at section

[technoe]

When setting a job to run a service, I get the error in the title.
I'm running ofelia as a service in docker swarm.
Here is my config.

[job-service-run "servie-executed-on-new-container"]
schedule = "* */10 * * *"
image = svc-backup:latest
network = traefik-network

[yuklia]

@technoe i faced the same issue

[adrian549092]

Same issue here, only difference is that I am targeting an existing service:

[job-service-run "Flask_Ingest_Data"]
schedule = 0 */15 * * * *
service= nops_app
command = flask ingest data
no-overlap = true

This is the output of the service logs

nops_cron.1.rhej4c43b7gf@ucs-nopsap-vm02    | warning:
nops_cron.1.rhej4c43b7gf@ucs-nopsap-vm02    | can't store data at section "job-service-run", subsection "Flask_Ingest_Data", variable "service"
nops_cron.1.rhej4c43b7gf@ucs-nopsap-vm02    |

[taraspos]

Hey, sorry. I'm not able to work on the issue now, and probably will not be able for the following month at least. If someone willing to investigate/fix it, I would be very happy to merge the fix :)

[taraspos]

So I was finally able to investigate this issue a bit.

So this looks like different issues:

1. @technoe @yuklia did you manage to find a workaround? I just tried to reproduce it locally and I cannot. I would need more detailed logs to figure out what is wrong. I see image = svc-backup:latest, which looks like a local image, and ofelia doesn't support local images as for now, see How to run a local image #55
2. @adrian549092 you are trying to run the job on the existing service, which is not supported not, but, as you discovered yourself, the proposed solution is in the PR Added option to run existing swarm service #49. The other problem here, that you specifying the command to run, which shouldn't be supported by running on existing service, because existing service already has command configured and changing it means updating service configuration.