Docker GUI plugin now stable

    I'd love some help understanding how to set up (well various) a docker container like this:


    https://hub.docker.com/r/jrottenberg/ffmpeg/
    https://github.com/jrottenberg/ffmpeg


    There doesn't seem to be any indication of what port to use, nor what folders I should be configuring..


    I tried just setting it to bridgemode, then pointing to a folder with some stuff I want to convert and mounting it as /input, and another folder where I'd like the output to go.. and mounting as '/output'
    but as soon as I start the container it stops..


    how would I get a container like the above set up so I can use it?

    • Offizieller Beitrag

    Those containers are not meant to run from the plugin because they run in interactive mode. The plugin fires all containers in daemon mode.


    For using those you need to drop down to terminal.


    I guess you can fire a container of ffmpeg with just a shell and two mount volumes input and output folder, then enter the container and run commands inside to transcode.


    But as i said the main purpose of those ones is for use in CLI

    Hi,
    First, I would to say thaks for all you effort on openmediavault.
    I would to try the docker plug-in on the last openmediavault 2, I think i forgot something because I don't have the docker plun ins in the list.


    ================================================================================
    = OS/Debian information
    ================================================================================
    Distributor ID: debian
    Description: Debian GNU/Linux 7 (wheezy)
    Release: 7.9
    Codename: wheezy


    ================================================================================
    = openmediavault information
    ================================================================================
    Release: 2.1.25
    Codename: Stone burner


    ================================================================================
    = System information
    ================================================================================
    Linux nas 3.16.0-0.bpo.4-686-pae #1 SMP Debian 3.16.7-ckt20-1+deb8u3~bpo70+1 (2016-01-19) i686 GNU/Linux


    I install backport kernel, active docker repository in omvextra , do an apt-clean and still nothing in plugin ...
    What have I miss? ?(

    Time for an update of the status of plugin. I've been working a lot with a new version that's compatible with OMV 3.x (when it's stable). Here is a summary of the new features/fixes added to the 3.x version of the plugin: (this version is only for TESTING so far).


    openmediavault-docker-gui (3.0.6)


    * Bug fixes to container and image backend
    * Rewrite to improve container and image listing performance
    * Fix for Image ID changes introduced in docker-engine 1.10
    * Add dependency on docker-engine >= 1.10


    openmediavault-docker-gui (3.0.5)


    * Make it possible to update linuxserver.io images from repo tab
    * Various bug fixes


    openmediavault-docker-gui (3.0.4)


    * Add timestamp to image object
    * Make it possible to modify running container


    openmediavault-docker-gui (3.0.3)


    * Minor tweaks to the repo tab
    * Add logos to the linuxserver.io docker images
    * Add php5-imagick dependancy
    * Make it possible to edit port forwarding rows
    * Make it possible to edit environment variable rows
    * Make it possible to edit bind mount rows
    * Make it possible to edit volumes from rows
    * Add tooltips to buttons
    * Add info button to repo tab entries
    * Reload repo tab when a new image is pulled
    * Make repo tab hidden if plugin is not enabled


    openmediavault-docker-gui (3.0.2)


    * Add r/o mode to bind mounts
    * Stability fixes to Docker service restart
    * Add linuxserver.io images to the repo tab
    * Usability improvements on the repo tab


    openmediavault-docker-gui (3.0.1)


    * Fix postrm script to use systemd
    * Add fixes to ensure proper upgrade from 0.2.x plugin branch


    openmediavault-docker-gui (3.0.0)


    * Make plugin OMV 3.x compatible
    * Add support for network port types (tcp/udp)
    * Rename "Docker repo" to "Docker images repo"
    * Make time sync with host default when running container
    * Make restart always policy default when running container


    Quite a lot of things... I hope you will like this new version when OMV 3.x is ready.

    I'm confused with the basic storage locations presented by docker-gui. I'm running OMV 3.0.6 on 16gb USB2 flash storage. How do I confirm or set the locations for each portion of docker?


    Several other omv plugins give me the option to place the default storage location on the MDRAID device.

    omv 3.0.7 erasmus | 64 bit | 4.3 backport kernel | omvextrasorg 3.0.9
    omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

    Running OMV 2.1.27 w/ 3.16 kernel. Docker-Gui 0.2.21 . So I am confused on passing mount points. I am trying to get SABnzbd to work. I have tried multiple forks, and current have the timhaak/sabnzbd installed. When I specify points under the Volumes and Bind Mounds, in this case /media/UUID/Folder/Folder as the host path and then /config for the container path(one of the autofill options), when I start the process it always says in SABnzbd that it's "Default Base Folder: /config" and after hunting it down, it's not even where I specified /config, it's /var/lib/docker/volumes/UUID/_data


    Any idea what I am doing wrong?

    • Offizieller Beitrag
    Zitat von RustyPitchfork

    No, I cannot say that I totally understand it.


    privileged is to pass hardware straight to the container, usb devices, block devices, audio devices etc as also kernel modules (like if you want to mount a nfs export inside a container)
    Host mode will run binded directly to eth0 interface. The idea of containers is isolation, the only case where you would need to run container in host mode (that i can think know) is with sw that requires to be in a same broadcast domain to work, UPNP, service discovery, etc. Like plex to be visible to iOS devices, kodi upnp, etc.


    Clearly sabnzbd is not a container that requires those things....but is up to you.

    I have a strange issue. I install the plugin but appear that i can't download any image or container. Below is the log file entries.


    time="2016-02-15T02:12:25.727750287+01:00" level=warning msg="/!\\ DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING /!\\"
    time="2016-02-15T02:12:25.734548828+01:00" level=info msg="[graphdriver] using prior storage driver \"aufs\""
    time="2016-02-15T02:12:25.735399125+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
    time="2016-02-15T02:12:25.741823746+01:00" level=info msg="Firewalld running: false"
    time="2016-02-15T02:12:26.439628131+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
    time="2016-02-15T02:12:26.970352443+01:00" level=warning msg="Your kernel does not support cgroup memory limit: mountpoint for memory not found"
    time="2016-02-15T02:12:26.970770427+01:00" level=warning msg="Your kernel does not support cgroup cfs period"
    time="2016-02-15T02:12:26.971329183+01:00" level=warning msg="Your kernel does not support cgroup cfs quotas"
    time="2016-02-15T02:12:26.974786420+01:00" level=info msg="Loading containers: start."


    time="2016-02-15T02:12:26.975055904+01:00" level=info msg="Loading containers: done."
    time="2016-02-15T02:12:26.975098216+01:00" level=info msg="Daemon has completed initialization"
    time="2016-02-15T02:12:26.975142424+01:00" level=info msg="Docker daemon" commit=9e83765 execdriver=native-0.2 graphdriver=aufs version=1.10.1
    time="2016-02-15T02:12:26.993441337+01:00" level=info msg="API listen on 127.0.0.1:42005"
    time="2016-02-15T02:12:26.993730657+01:00" level=info msg="API listen on /var/run/docker.sock"
    time="2016-02-15T02:13:13.671462226+01:00" level=error msg="Couldn't run auplink before unmount: exec: \"auplink\": executable file not found in $PATH"
    time="2016-02-15T02:19:55.355400277+01:00" level=error msg="Handler for POST /v1.22/images/create returned error: Error parsing HTTP response: invalid character '<' looking for beginning of value: \"<html><body><h1>408 Request Time-out</h1>\\nYour browser didn't send a complete request in time.\\n</body></html>\\n\\n\""


    from the info:


    Containers: 0
    Running: 0
    Paused: 0
    Stopped: 0
    Images: 0
    Server Version: 1.10.1
    Storage Driver: aufs
    Root Dir: /var/lib/docker/openmediavault/aufs
    Backing Filesystem: zfs
    Dirs: 0
    Dirperm1 Supported: true
    Execution Driver: native-0.2
    Logging Driver: json-file
    Plugins:
    Volume: local
    Network: bridge null host
    Kernel Version: 3.16.0-0.bpo.4-amd64
    Operating System: Debian GNU/Linux 7 (wheezy)
    OSType: linux
    Architecture: x86_64
    CPUs: 4
    Total Memory: 15.68 GiB
    Name: NASBox
    ID: DHQT:YEZB:E575:UP2T:SL2C:WAUO:E54Z:P3HX:VPCM:QBVH:WYRP:Z5WK
    WARNING: No memory limit support
    WARNING: No swap limit support
    WARNING: No oom kill disable support
    WARNING: No cpu cfs quota support
    WARNING: No cpu cfs period support


    any help?

    Basically I haven't touch anything except adding storage path and enable the plugin. Nothing more.
    CLI gives basically the same error. GUI doesn't show anything.


    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    E: Unable to locate package aufs-utils


    I have install aufs-tools

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden