• progress_activity cloud_sync

    Reconnection to the server…

    Movim cannot talk with the server, please try again later

  • back_to_tab fullscreen tile_small dialpad mic videocam switch_camera screen_share

    mic_none No sound detected from your microphone


    • GadgeteerZA Tech Blog

      My GadgeteerZA tech and gadgets blog posts

      article 1651 posts • people 76 subscribers
      assignment_ind Only publishers can publish


    • Public subscriptions

    • chevron_right

      Andrath of the Abyss

  • Register Login

    Movim

    deimos.hackerheaven.org


  • rss_feed
    add Follow

    GadgeteerZA Tech Blog

    people 76 subscribers • My GadgeteerZA tech and gadgets blog posts

    • chevron_right

      3 Ways to Define Docker Volumes Explained in 6 Minutes

      news.movim.eu / gadgeteerza-tech-blog • 21 March 2022

    Docker containers are great (my opinion) due to their ease of deployment and updating, as well as better resource usage for multiple concurrent services on a server. One could also argue they offer better security due to the potential ways you can isolate them from each other, and even your network (see an upcoming video of mine about this point).

    A docker container on its own though does not retain any transactional data (persistence) if it is destroyed or updated. To achieve persistence, one creates volumes, which essentially map locations out to the OS side. Destroy or update the container, and it can still read that data from the volume.

    This video explains quite clearly the 3 different ways to define such volumes.

    Watch https://youtu.be/p2PH_YPCsis

    #technology #docker #container #volume #storage

    • https://www.youtube.com/supported_browsers?next_url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dp2PH_YPCsis&feature=youtu.be

      youtu.be

    • tagdocker tagcontainer tagvolume tagstorage

    • Pictures 1 image

    • visibility
  • cloud_queue

    Powered by Movim