Docker is steaming pile of πŸ’©



  • @heterodox said in Docker is steaming pile of πŸ’©:

    I feel like I'm the only one lurking in this thread who's really never had a problem with Docker and for whom Docker has been very convenient. πŸ€·πŸΌβ™‚

    You are not I have worked on a number of complex systems that were based on many Docker images. But, I will admit designing/creatinging/maintaining a system is a different environment than using randomly created and downloaded containers...

    I also have never had problems with Git losing my data. I

    Neither have I... Though I have had far too many cases of humans doing stupid things (for a variety of raisins) that resulted in data being stored in Git being corrupted/destroyed/lost.



  • @bulb said in Docker is steaming pile of πŸ’©:

    They are not building any packages.

    My bad. It's Japaric (whatever that is) that can't figure out how to build a Deb package.



  • @shoreline said in Docker is steaming pile of πŸ’©:

    significant percentage of that restarting docker

    On Linux not. On Windows, totally. On Windows it also never starts properly later on after the computer is up for some time, so every time it crashes, it takes restarting the whole computer to get it back up. Also two of three times it offered me an upgradeβ€”and I was foolish enough to approve itβ€”it shat up the kubernetes installation and it couldn't be fixed except by uninstalling, manually removing the virtual machine image and reinstalling. Just because.

    @shoreline said in Docker is steaming pile of πŸ’©:

    The one thing I would say about it is that the problem is usually a docker problem rather than an OS problem.

    I would say the problems I've seen are usually problem of how the docker service (mis)manages the virtual machine in which the actual containers live. That thing is definitely part of Docker, but it only exists on Windows and MacOS. On Linux, I didn't see much problems except the very old version not understanding images built with a much newer one.


  • Impossible Mission - B

    @topspin said in Docker is steaming pile of πŸ’©:

    Was he, by chance, talking about NodeJS or "desktop" apps which are just a web view of a web app?

    No, this was given in the 70s IIRC. It remains relevant to this day, as does most of his talk.



  • @timebandit said in Docker is steaming pile of πŸ’©:

    @bulb said in Docker is steaming pile of πŸ’©:

    They are not building any packages.

    My bad. It's Japaric (whatever that is) that can't figure out how to build a Deb package.

    I suspect Japaric could build them. However, it would require upgrading rather large part of the environment in Travis. See, the issue actually started with the Qemu packages in Trusty Tahr being too old and not actually working. And upgrading those requires upgrading a bunch of other things, and then installing some toolchains. And then the result would work on Travis, but when somebody develops locally on Red Death or whatever, they would need different packages to try it locally. The Docker image works everywhere as long as there is sufficiently new docker, which Travis does have, because everybody wants that these days. Running the images is quite complicated, but that's why it's wrapped in a tool anyway.


  • BINNED

    @bulb
    So the usual dance of I solved my issue by throwing more tools at it and now I have two issues and a pile of tools on the floor ...



  • @bulb said in Docker is steaming pile of πŸ’©:

    the issue actually started with the Qemu packages in Trusty Tahr being too old and not actually working.

    IOW, the problem is Ubuntu πŸ™„



  • @luhmann Actually, no. Throwing more tools at it failed, so a one, different tool was thrown on it and it works much better.


Log in to reply