[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI

Barak Korren (oVirt JIRA) jira at ovirt-jira.atlassian.net
Sun Feb 26 08:47:43 UTC 2017


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27805#comment-27805 ] 

Barak Korren commented on OVIRT-892:
------------------------------------

Turns out Docker deamon is not willing to run from inside mock, so option #3 becomes useless. 
To fail as in option #1 is probably useful only when someone is creating brand-new CI scripts, so maybe no that important.

We implemented a [patch|https://gerrit.ovirt.org/#/c/72991/] that detects if we're trying to mount a socket file instead of a directory and make sure that works. This solves the issue of mounting the Docket socket.

> Allow for optional bind mounts in Standard-CI
> ---------------------------------------------
>
>                 Key: OVIRT-892
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: Barak Korren
>            Assignee: infra
>              Labels: containers, docker, standard-ci
>
> Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist.
> We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead.
> We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options:
> # Fail - what it used to do
> # Create what it needs - what it does now
> # Just ignore and not mound
> Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)


More information about the Infra mailing list