Docker images for using openmediavault-docker-gui as plugin manager

  • As I already said here : Plugin Docker is a non-maintained docker plugin. The work done by Nicjo814 it's just great !
    The plugin works like a charm ! Plugin main discussion here : Docker GUI plugin now stable


    Once the plugin installed, you have some preferred images you can get in the plugin. One of them is done by me (scm-manager). It's fully compatible with openmediavault, because I've done the necessary in the dockerfile to have a subdirectory to allow nginx redirection.
    With that way, you can keep openmediavault uri (and https) and redirect to the docker port/protocol. But, I need to maintain the docker file and so the docker project linked to the code source of the original project ... it can be sometimes a lot of work, and if nobody do this job on the docker images you want, if you don't know how to make your own ... there is no solution.


    So, may be not for all docker images, but for most of them, you should be able to redirect a subdirectory to the root of the container ... after some research, this is the way how to do this, with this procedure, you don't have to modify the docker image, just redirect all from a subdirectory to the container (most of the time, the container answer on the root).


    So, If I take the following service named my_docker_service, you have to pull image : maintenainer/my_docker_service tag : latest)


    After running the container from this image (exposing port : 80 ; mapped port 80XX) in this example.
    You have to add the following file /etc/nginx/openmediavault-webgui.d/my_docker_service.conf

    Code: /etc/nginx/openmediavault-webgui.d/my_docker_service.conf
    location /my_docker_service {
            rewrite ^/my_docker_service(/.*)$ $1 break;
            proxy_pass         http://localhost:80XX;
            proxy_set_header   Host localhost:80XX;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto https;
            proxy_redirect    default;
    }



    I just reload nginx :


    Bash
    service nginx reload

    Then you should be able to access to Shaarli container directly with the following url : https://your.openmediavault.org/my_docker_service/ instead of : http://your.openmediavault.org:8032/


    By this way, no need to duplicate my_docker_service github repository to adapt the image then publish it on docker repository ...


    So I purpose you to add in this discussion all docker images checked by this way and create a docker service catalog omv-compatible !

  • Shaarli : The personal, minimalist, super-fast, database free, bookmarking service
    Status
    :thumbup: Validated - in use


    Description
    Project : https://github.com/shaarli/Shaarli/
    Private service alternative : https://del.icio.us/
    Official Docker image : https://store.docker.com/community/images/shaarli/shaarli


    Docker prerequisite


    NGinx prerequisite



    Shaarli Service Access


    Then you should be able to access to Shaarli container directly with the following url : https://your.openmediavault.org/shaarli/ 


    Backup



    Troubles
    :!: If you have any trouble linked to this docker image procedure, please open a new discussion then I'll link it here.

  • Transmission throw VPN : Transmission is a cross-platform BitTorrent client
    Status
    :thumbup: Validated - In use


    Description
    Project : http://transmissionbt.com/about/
    Private service alternative :
    Non-Official Docker image : https://hub.docker.com/r/haugene/transmission-openvpn and https://hub.docker.com/r/haugene/transmission-openvpn-proxy



    Docker prerequisite


    Network and main container. Why should I create a network and the container linked to it ? Because we will use the vpn connection of this container wiith others : Jackett, SickBeard and couchPotato


    As you can see, we don't map any port. How to acces to Transmission ??? Throw a nginx proxy linked to the transmission-network.



    NGinx prerequisite



    Transmission Service Access


    Then you should be able to access to Transmission container directly with the following url : https://your.openmediavault.org/transmission/  and set your login/password !


    Backup


    Troubles
    If you have any trouble linked to this docker image procedure, please open a new discussion then I'll link it here.

  • SCM-Manager : The easiest way to share and manage your Git, Mercurial and Subversion repositories over http
    Status
    :?: To validate - In use


    Description
    Project : https://www.scm-manager.org/
    Private service alternative : https://github.com/
    Official Docker image : https://hub.docker.com/r/sdorra/scm-manager/


    Docker prerequisite


    NGinx prerequisite



    SCM Manager Service Access


    Then you should be able to access to Scm-manager container directly with the following url : https://your.openmediavault.org/scm/ 


    Backup


    Troubles
    If you have any trouble linked to this docker image procedure, please open a new discussion then I'll link it here.

  • Teampass : TeamPass is a Passwords Manager dedicated for managing passwords in a collaborative way


    Status
    :!: Test in progress


    Description
    Project : http://teampass.net/
    Private service alternative : https://lastpass.com/
    Official Docker image : https://store.docker.com/community/images/teampass/teampass/


    Docker prerequisite


    NGinx prerequisite



    Teampass Service Access


    Then you should be able to access to Teampass container directly with the following url : https://your.openmediavault.org/teampass/ 


    Backup


    Troubles
    If you have any trouble linked to this docker image procedure, please open a new discussion then I'll link it here.

Jetzt mitmachen!

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