ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Topics on the Merits and Downfalls of Containerization

    IT Discussion
    docker containerization container applications
    5
    23
    4.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403
      last edited by DustinB3403

      To play the devils advocate here: If an application so valuable must be built into a container (such as Docker) and you build it on Ubuntu for example, wouldn't maintaining it be very simple.

      You download it and go. Download the updated one and go. Rinse and Repeat as the software is updated. Yes the old version is there, but why wouldn't you update if you had it there.

      This seems a lot like "you're building Frankenstein, by allowing an application to be around well past the supported OS has gone."

      scottalanmillerS 2 Replies Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @DustinB3403
        last edited by

        @DustinB3403 said:

        To play the devils advocate here: If an application so valuable must be built into a container (such as Docker) and you build it on Ubuntu for example, wouldn't maintaining it be very simple.

        Not if designed properly. Or should I saw "as designed."

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @DustinB3403
          last edited by

          @DustinB3403 said:

          You download it and go. Download the updated one and go. Rinse and Repeat as the software is updated. Yes the old version is there, but why wouldn't you update if you had it there.

          Because containers are not designed to be logged into or updated. It's conceptually not how they are meant to be used. So you would need people mistreating them as VMs and really defeating the purpose in order to make that possible and then you'd have to ask... why are we doing this?

          stacksofplatesS 1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

            By "maintained" I mean, you go and download the updated container and be done with it.

            You'd simply delete the "old" one.

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @DustinB3403
              last edited by

              @DustinB3403 said:

              By "maintained" I mean, you go and download the updated container and be done with it.

              You'd simply delete the "old" one.

              Oh okay. That works fine in scenarios where you are deploying code containerized by others. Everyone I've worked with deploying Docker is using it to deploy their own code.

              1 Reply Last reply Reply Quote 0
              • stacksofplatesS
                stacksofplates @scottalanmiller
                last edited by

                @scottalanmiller said:

                @DustinB3403 said:

                You download it and go. Download the updated one and go. Rinse and Repeat as the software is updated. Yes the old version is there, but why wouldn't you update if you had it there.

                Because containers are not designed to be logged into or updated. It's conceptually not how they are meant to be used. So you would need people mistreating them as VMs and really defeating the purpose in order to make that possible and then you'd have to ask... why are we doing this?

                I know Docker is that way, but I don't think that's how LXC is designed to be used. You set up the container and use either lxc-attach or lxc-console to connect to a tty.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  Correct, LXC is an old, traditional container like we've used for a decade or more and is just like any other VM technology. You can ignore that it is a container 🙂

                  1 Reply Last reply Reply Quote 1
                  • stacksofplatesS
                    stacksofplates
                    last edited by

                    I think for SMB and some other places LXC, jails, and zones make sense. However Docker does seem like it would be more work than it's worth.

                    I've heard Rocket is supposed to be easier than Docker, but I haven't had a chance to play with it (or really had a reason to).

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @stacksofplates
                      last edited by

                      @johnhooks Docker is great for DevOps shows and totally built for them. Zones, Jails and LXC are for big UNIX admins to use for super high performance VMs. 🙂

                      dafyreD 1 Reply Last reply Reply Quote 1
                      • scottalanmillerS
                        scottalanmiller
                        last edited by

                        Yup, I have heard that about Rocket but have not had a chance to look at it. Can't wait for the lab to be up!!

                        1 Reply Last reply Reply Quote 1
                        • dafyreD
                          dafyre @scottalanmiller
                          last edited by

                          @scottalanmiller said:

                          @johnhooks Docker is great for DevOps shows and totally built for them. Zones, Jails and LXC are for big UNIX admins to use for super high performance VMs. 🙂

                          It seems like lxc & family are soon to get live migration as well...

                          1 Reply Last reply Reply Quote 1
                          • scottalanmillerS
                            scottalanmiller
                            last edited by

                            Yeah, some definitely will.

                            dafyreD 1 Reply Last reply Reply Quote 0
                            • dafyreD
                              dafyre @scottalanmiller
                              last edited by

                              @scottalanmiller said:

                              Yeah, some definitely will.

                              I wonder what that will do against Virtualization platforms like XenServer, VMware, et al...

                              if an lxc-container is functionally equivalent to a VM... Would it be possible to run Windows in an lxc-container... That type of thing.

                              scottalanmillerS 1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @dafyre
                                last edited by

                                @dafyre said:

                                @scottalanmiller said:

                                Yeah, some definitely will.

                                I wonder what that will do against Virtualization platforms like XenServer, VMware, et al...

                                if an lxc-container is functionally equivalent to a VM... Would it be possible to run Windows in an lxc-container... That type of thing.

                                No, we've had those containers for a decade and we are nowhere near having Windows in them. They all share the parents' kernel by definition. So no Windows coming on Linux containers. Much closer to PV Windows on Xen, at least that has been done in a lab.

                                DustinB3403D dafyreD 2 Replies Last reply Reply Quote 0
                                • DustinB3403D
                                  DustinB3403 @scottalanmiller
                                  last edited by

                                  @scottalanmiller said:

                                  No.... They all share the parents' kernel by definition.

                                  So does the container get the same security updates that the host is due for? What if one of those updates is a newer version of the contained application?

                                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                                  • dafyreD
                                    dafyre @scottalanmiller
                                    last edited by

                                    @scottalanmiller said:

                                    @dafyre said:

                                    @scottalanmiller said:

                                    Yeah, some definitely will.

                                    I wonder what that will do against Virtualization platforms like XenServer, VMware, et al...

                                    if an lxc-container is functionally equivalent to a VM... Would it be possible to run Windows in an lxc-container... That type of thing.

                                    No, we've had those containers for a decade and we are nowhere near having Windows in them. They all share the parents' kernel by definition. So no Windows coming on Linux containers. Much closer to PV Windows on Xen, at least that has been done in a lab.

                                    What about Containerization on Windows? Didn't OpenVZ or Virtuozzo...used to offer something like that?

                                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @DustinB3403
                                      last edited by

                                      @DustinB3403 said:

                                      @scottalanmiller said:

                                      No.... They all share the parents' kernel by definition.

                                      So does the container get the same security updates that the host is due for? What if one of those updates is a newer version of the contained application?

                                      No, the DevOps model, and by extension the Docker model, is that the containers never get updates, never change. They are disposable. You replace them, you do not update or maintain them. Same as Devops with Vms.

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @dafyre
                                        last edited by

                                        @dafyre said:

                                        @scottalanmiller said:

                                        @dafyre said:

                                        @scottalanmiller said:

                                        Yeah, some definitely will.

                                        I wonder what that will do against Virtualization platforms like XenServer, VMware, et al...

                                        if an lxc-container is functionally equivalent to a VM... Would it be possible to run Windows in an lxc-container... That type of thing.

                                        No, we've had those containers for a decade and we are nowhere near having Windows in them. They all share the parents' kernel by definition. So no Windows coming on Linux containers. Much closer to PV Windows on Xen, at least that has been done in a lab.

                                        What about Containerization on Windows? Didn't OpenVZ or Virtuozzo...used to offer something like that?

                                        You can, in theory, make Windows containers on Windows. But you have to be on Windows already.

                                        1 Reply Last reply Reply Quote 0
                                        • 1
                                        • 2
                                        • 2 / 2
                                        • First post
                                          Last post