job executor run options with podman instead of docker (OD-2159)
bufferUnderrun opened 1 year ago

Hi Robin,

I'm using podman as the underlying container executor for both running 1dev/server image and also all build launch by onedev itself (thanks to -v %t/podman/podman.sock:/var/run/docker.sock).

Podman is constantly evolving and i need to add some options to continue running build smoothly. One of them is the --net=slirp4netns which set the old network behavior for podman 5.0. Later for podman 5.3 there are others interesting argument to tune the pasta network driver.

I try with "more settings" from the job executor settings but this does not work.

2024-11-08 00_59_40-Administration - OneDev — Mozilla Firefox.png

Could it be possible to have run options for podman ?

Thanks for you help

  • Robin Shen commented 1 year ago

    OneDev does add these options to docker command line. Supporting podman seems very troublesome, and I can only support docker considering limited resource.

  • Robin Shen changed state to 'Closed' 1 year ago
    Previous Value Current Value
    Open
    Closed
  • bufferUnderrun commented 1 year ago

    I understand you have limited resources and can only support officially docker.

    So i'm not asking to support officially podman but instead trying to figure out how the settings are working. And with a huge number of parameters in common a docker alias from podman works out of the box for quite all use cases.

    In recent release of Podman, i need to add a parameter --net=slirp4netns in the run command.

    For me, it should works as the docker parameters but i got error.

    To help me debugging, could it be possible to :

    • add to the debug log, the full command line OneDev is calling to run the container of the build step.
    • maybe add an extra help to show more precisely the command onedev will run image.png

    Thanks for your help

  • bufferUnderrun changed state to 'Open' 1 year ago
    Previous Value Current Value
    Closed
    Open
  • Robin Shen commented 1 year ago

    You may add below line to conf/logback.xml:

    <logger name="io.onedev.commons.utils.command" level="DEBUG"/>
    

    Then restart OneDev server, run build and check server log.

  • Robin Shen changed state to 'Closed' 1 year ago
    Previous Value Current Value
    Open
    Closed
  • Robin Shen commented 1 year ago

    I am closing this as podman is out of OneDev support. If run options are not appended to docker command as expected, please open another issue.

issue 1/1
Type
Improvement
Priority
Normal
Assignee
Labels
No labels
Issue Votes (0)
Watchers (2)
Reference
OD-2159
Please wait...
Connection lost or session expired, reload to recover
Page is in error, reload to recover