- Northern Italy
- https://coolsoft.altervista.org
- Joined on
2023-07-06
This issue is similar to this other one (I'd like to inject Docker configuration params into started containers).
I've a…
15045b4fc0
Merge pull request 'Fix panic in extractFromImageEnv' (#81) from wolfogre/act:bugfix/panic_extractFromImageEnv into main
this issue looks like it is already fixed
No, it's not. options are applied only to default container.
If you use a custom container to run your jobs (and it happens most of the…
Is there any possible security problem of this patch?
Which kind of problem are you suspecting could be introduced?
In my mind config.yaml file and its container.options field is…
I've already posted my own fix 3 months ago to the issue you've mentioned. Nobody commented...
Now I've created a PR [here](https://gitea.com/gi…
Here you are.
I've also patched it to let it work with Gitea 1.20+ (see lines 271-272):
--color-nav-bg: var(--color-body);
--color-nav-hover-bg: var(--color-hover);
Sometimes you just want to inject the same options to all started containers (e.g. corporate proxy settings), so it's better to "force" them through act_runner instead of repeating the same…
Looking at the code I've found that container.options in runner config.yaml file are applied only to default container; if a job has custom container configured, then it receives only…
you could try to add the option string to
jobs.<job_id>.container.optionsand it should work.
I have the same issue and this "fixed" it but...
On my side I need to apply some **special…