​who can help me to run this image correctly?

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • nicovon wrote:

      who can help me to run this image correctly?
      What have you tried? Have you watched any of the docker videos to see how just about every one of them translates what you find on docker hub into parameters on the plugin?
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • First I ran the following command:

      Source Code

      1. docker pull garethflowers/svn-server

      Then:

      Source Code

      1. docker run \
      2. --name serversvn \
      3. --detach \
      4. --volume /home/svn:/var/opt/svn \
      5. --publish 3690:3690 \
      6. garethflowers/svn-server
      So for now I have been following the developer's instructions. I have not yet figured out if I'm doing well or not and above all what is the next step. I would like someone to clarify my doubts, for me it is the first time with docker and also with a versioning system.

      The post was edited 2 times, last by nicovon ().

    • And then? Did you create a repo with docker exec -it and the svnadmin command? Does /home/svn exist on your server? What isn't working?
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • nicovon wrote:

      no, I haven't created a repo yet.
      It won't do anything without a repo.

      nicovon wrote:

      I don't know if /home /svn exists
      If you didn't create it, it doesn't exist. ls -al /home/ will tell you but most people use a path that you know exists. All of the docker videos show how to do this.

      nicovon wrote:

      Is it a problem if it doesn't exist?
      If you need to keep your svn repo(s) after the docker container shuts down, it is very important.
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      nicovon wrote:

      I don't know if /home /svn exists
      If you didn't create it, it doesn't exist. ls -al /home/ will tell you but most people use a path that you know exists. All of the docker videos show how to do this.
      looks like it already exists:

      Source Code

      1. root@omv:~# ls -al /home/
      2. total 12
      3. drwxr-xr-x 3 root root 4096 Nov 11 09:53 .
      4. drwxrwxr-x 24 root root 4096 Nov 4 08:32 ..
      5. drwxr-xr-x 2 root root 4096 Nov 11 09:53 svn
      I tried to create a new repository but I didn't understand if it's enough to just start the container, or you have to start the image first.

      Source Code

      1. root@omv:~# docker exec -it serversvn svnadmin create vbrepo
      2. Error response from daemon: Container 574b39991e00c1ccdc23db8e5695d8cf3c687a039961dd6b0ef41a0ef41cac25 is not running

      The post was edited 2 times, last by nicovon ().

    • nicovon wrote:

      I didn't understand if it's enough to just start the container, or you have to start the image first.
      You can't start an image. You can start a container using an image. You definitely have to have the container running to exec into it.
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • nicovon wrote:

      The omv web gui allows me to start the image, as shown here
      That pic doesn't show the container running. That just creates the container. The status should be in the grid at the bottom of the plugin. Did you start the container in the bottom grid?
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      That pic doesn't show the container running. That just creates the container. The status should be in the grid at the bottom of the plugin. Did you start the container in the bottom grid?
      then this button: imgur.com/wDVA16Q
      is it equivalent to executing these commands?:

      Source Code

      1. docker run \
      2. --name serversvn \
      3. --detach \
      4. --volume /home/svn:/var/opt/svn \
      5. --publish 3690:3690 \
      6. garethflowers/svn-server

      @ryecoaaron yes, now I started the container.
      the value "STATE" is "running" and the value "STATUS" is "Up 5 minutes (healthy)".
      then I ran the command again:

      Source Code

      1. docker exec -it serversvn svnadmin create vbrepo
      seems to have worked because it didn't return me anything.


      but now what should I check and test?

      The post was edited 1 time, last by nicovon ().

    • Source Code

      1. C:\Users\user>ping omv
      2. Esecuzione di Ping omv [10.0.30.22] con 32 byte di dati:
      3. Risposta da 10.0.30.22: byte=32 durata<1ms TTL=64
      4. Risposta da 10.0.30.22: byte=32 durata<1ms TTL=64
      5. Risposta da 10.0.30.22: byte=32 durata<1ms TTL=64
      6. Risposta da 10.0.30.22: byte=32 durata<1ms TTL=64
      7. Statistiche Ping per 10.0.30.22:
      8. Pacchetti: Trasmessi = 4, Ricevuti = 4,
      9. Persi = 0 (0% persi),
      10. Tempo approssimativo percorsi andata/ritorno in millisecondi:
      11. Minimo = 0ms, Massimo = 0ms, Medio = 0ms
      Display All
      @ryecoaaron If I visit this address: 10.0.30.22:3690/
      a page with this text is returned to me:


      Source Code

      1. ( success ( 2 2 ( ) ( edit-pipeline svndiff1 accepts-svndiff2 absent-entries commit-revprops depth log-revprops atomic-revprops partial-replay inherited-props ephemeral-txnprops file-revs-reverse list ) ) )
    • nicovon wrote:

      should network mode be bridge?
      Sure.

      nicovon wrote:

      can the ip host be 0.0.0.0?
      Yes. That just means it is listening on all addresses that the system has.

      nicovon wrote:

      I didn't understand the difference between host path and container path.
      It is the mapping relationship between the path inside the container and outside the container. If the container reads or writes to the container path, it is actually reading/writing to the the specified host path. Perhaps you need to read more about containers.

      nicovon wrote:


      I didn't understand exactly what I'm going to save in /home/svn.
      You won't save anything in /home/svn. That is where svn server files will live so that you don't lose anything when the container restarts.

      nicovon wrote:

      a page with this text is returned to me:
      What were you expecting to see? You are interacting directly with svnserve on that port.

      Why again do you want an svn server?
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • nicovon wrote:

      is the container stopped when omv is turned off?
      Isn't everything turned off when OMV is turned off? That said, there is a restart policy in the plugin to restart the container automatically when OMV is rebooted.
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • nicovon wrote:

      does the container, on restart, remain stopped by default?
      Yes. The "Restart Policy" defaults to No which means the container will not start automatically on reboot. Most people change it to "unless stopped" if they want the container to start automatically on reboot.

      nicovon wrote:

      It seems then that this policy does not work. How can I check?
      This is extremely well tested and I have not heard of it not working. From your screenshot in your first post, you left the Restart Policy set to No. So, I think the container is doing what it is supposed to.
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Users Online 1

      1 Guest

    • Tags