Skip to content

Runner container volume mounts can't be configured due to missing HostConfig #521

@cdavernas

Description

@cdavernas

I tried this:

Configure the volume mounts of the runner containers spawned to execute workflows.

This happened:

The operator did not provide a way to configure volume mounts for runner containers because it only exposed the container configuration (Config) and not the host configuration (HostConfig). As a result, there was no way to define bind mounts or volume sources, making it impossible to mount external paths into the container at runtime.

I expected this:

I expected the operator to expose both ContainerTemplate (aka Config) and HostConfig so that volume mounts could be configured as part of the runner container specification. This would allow workflows to define bind mounts or named volumes and have them correctly applied at runtime.

Is there a workaround?

No response

Anything else?

This limitation has been pointed out by @ericlacher in #510 (comment).

Thank you @ericlacher ❤️

Platform(s)

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞

Metadata

Metadata

Assignees

Labels

app: operatorConcerns the Operatorpriority: highIndicates a high priority issueruntime: dockerConcerns the Docker Runtime Hosttype: bugSomething isn't workingweight: 2An issue with a low development impact

Type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions