Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-7320

FIWARE.Request.Tech.Cloud.Docker.FDCS VM restart

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      I'm starting with FDCS and i have followed this
      <http://fiware-docker-container-service.readthedocs.io/en/latest/userguide/u
      ser-guide/index.html#quick-start>
      http://fiware-docker-container-service.readthedocs.io/en/latest/userguide/us
      er-guide/index.html#quick-startguide.

      1.

      ./set_docker_conf.sh -d ~/.docker -t "lprunella cloud" -u
      <nicola.prunella@terasrl.it> nicola.prunella@terasrl.it-p Psynergia1
      -a cloud.lab.fi-ware.org:4730

      2.

      <root@formica-VirtualBox:~/.docker>
      root@formica-VirtualBox:~/.docker#cat config.json
      {
      "HttpHeaders":

      { "X-Auth-TenantId": "b85cedef9c964ee7b7b77d1ed1845e71", "X-Auth-Token": "59894088e8514d7eb8583e9ef498a88b" }

      }
      3.

      docker --config ~/.docker network create --driver bridge isolated_nw
      docker --config ~/.docker network inspect isolated_nw

      docker --config ~/.docker run --net=isolated_nw -itd -p 80 --name=container1
      busybox sh -c "httpd;sh"
      docker --config ~/.docker run --net=isolated_nw -itd -p 80 --name=container2
      busybox sh -c "httpd;sh"
      docker --config ~/.docker network inspect isolated_nw

      docker --config ~/.docker exec container1 ping -W 1 -c 3 container2

      docker --config ~/.docker ps

      docker --config ~/.docker network ls

      user1_container1_URL=$(docker --config ~/.docker port container1 80)
      user1_container2_URL=$(docker --config ~/.docker port container2 80)

      $ curl -s $user1_container1_URL > /dev/null && echo connected || echo Fail
      connected
      $ curl -s $user1_container2_URL > /dev/null && echo connected || echo Fail
      connected

      All is going ok and I have checked that the above containers are up and
      running, but if I restart by VM whereI have issued the above command I
      cannot find any running container with docker --config ~/.docker ps.

      The doubt is : have I run effectively these container on Fiware FDCS ?

      Thank you

      Best Regards

      cid:image001.png@01D1EDAF.8BF11F70

      NICOLA PRUNELLA

      Software Engineer

      M.: +39 335 7174081

      <nicola.prunella@terasrl.it> nicola.prunella@terasrl.it

      <https://www.linkedin.com/company/tera-srl>
      cid:image002.jpg@01D1EDAF.8BF11F70 <https://twitter.com/terasrl/>
      cid:image003.jpg@01D1EDAF.8BF11F70
      <https://www.facebook.com/terasrl/?ref=settings>
      cid:image004.jpg@01D1EDAF.8BF11F70
      <https://www.youtube.com/channel/UCEL7okanxt_JFt3YJUrV6cg>
      cid:image005.jpg@01D1EDAF.8BF11F70

      cid:image002.jpg@01D1EDAF.8BF11F70 <https://twitter.com/lprunella>
      cid:image006.jpg@01D1EDAF.8BF11F70cid:image004.jpg@01D1EDAF.8BF11F70
      <skype:> cid:image007.jpg@01D1EDAF.8BF11F70

      TERA SRL

      Via Cesare Balbo 19/D,

      70014, Conversano (BA),

      Italy

      P.: +39 080 2147775

      <http://www.terasrl.it> www.terasrl.it

      <info@terasrl.it> info@terasrl.it

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help
      [Created via e-mail received from: nicola.prunella@terasrl.it]

      1. image001_01D213258E60C530.png
        4 kB
      2. image002_01D213258E60C530.jpg
        0.8 kB
      3. image003_01D213258E60C530.jpg
        0.8 kB
      4. image004_01D213258E60C530.jpg
        0.8 kB
      5. image005_01D213258E60C530.jpg
        0.8 kB
      6. image006_01D213258E60C530.jpg
        0.8 kB
      7. image007_01D213258E60C530.jpg
        0.8 kB

        Activity

        Hide
        knagin Kenneth Nagin added a comment -

        I think the problem is that the DOCKER_HOST is no longer pointing to FDCS when you restart the VM.

        Show
        knagin Kenneth Nagin added a comment - I think the problem is that the DOCKER_HOST is no longer pointing to FDCS when you restart the VM.
        Hide
        knagin Kenneth Nagin added a comment -

        The user contacted me directly. The problem is fixed.

        Show
        knagin Kenneth Nagin added a comment - The user contacted me directly. The problem is fixed.

          People

          • Assignee:
            knagin Kenneth Nagin
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: