home.social

#containerized — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #containerized, aggregated by home.social.

  1. Welcome project to the Cloud Native Computing Foundation! Just in time for 😁
    This is the first time the has adopted an distribution.
    Now we've got a distro for workloads!
    linkedin.com/feed/update/urn:l

  2. Welcome #Flatcar project to the Cloud Native Computing Foundation! Just in time for #kubecon 😁
    This is the first time the #CNCF has adopted an #operatingSystem distribution.
    Now we've got a #Linux distro for #cloudnative #containerized workloads!
    linkedin.com/feed/update/urn:l

  3. Welcome #Flatcar project to the Cloud Native Computing Foundation! Just in time for #kubecon 😁
    This is the first time the #CNCF has adopted an #operatingSystem distribution.
    Now we've got a #Linux distro for #cloudnative #containerized workloads!
    linkedin.com/feed/update/urn:l

  4. Welcome #Flatcar project to the Cloud Native Computing Foundation! Just in time for #kubecon 😁
    This is the first time the #CNCF has adopted an #operatingSystem distribution.
    Now we've got a #Linux distro for #cloudnative #containerized workloads!
    linkedin.com/feed/update/urn:l

  5. Welcome #Flatcar project to the Cloud Native Computing Foundation! Just in time for #kubecon 😁
    This is the first time the #CNCF has adopted an #operatingSystem distribution.
    Now we've got a #Linux distro for #cloudnative #containerized workloads!
    linkedin.com/feed/update/urn:l

  6. I like #Audible, but I also prefer to have my audiobooks on my own storage. Luckily there is #OpenAudible that can download my legally purchased titles, and #AudiobookShelf that can help me organize and listen to them - even when I'm on the road. Recently I've discovered that OpenAudible comes in a #containerized version, which is right up my alley - I could run it on my Synology NAS, access it from anywhere and not worry about files filling up my laptop or desktop system. Now here's the amusing part: sure the OpenAudible guys have provided a "containerized" version, but it's done in all the wrong ways: it's still running their Java application, but wrapped in an HTTP-enabled remote desktop client that accesses a Linux desktop, which is also running in the container. There's even an SSH server running there. Guys, while your application is most excellent, you have many things to learn about containers - full fat VM-like containers is not how you do it.

  7. I like #Audible, but I also prefer to have my audiobooks on my own storage. Luckily there is #OpenAudible that can download my legally purchased titles, and #AudiobookShelf that can help me organize and listen to them - even when I'm on the road. Recently I've discovered that OpenAudible comes in a #containerized version, which is right up my alley - I could run it on my Synology NAS, access it from anywhere and not worry about files filling up my laptop or desktop system. Now here's the amusing part: sure the OpenAudible guys have provided a "containerized" version, but it's done in all the wrong ways: it's still running their Java application, but wrapped in an HTTP-enabled remote desktop client that accesses a Linux desktop, which is also running in the container. There's even an SSH server running there. Guys, while your application is most excellent, you have many things to learn about containers - full fat VM-like containers is not how you do it.

  8. I like #Audible, but I also prefer to have my audiobooks on my own storage. Luckily there is #OpenAudible that can download my legally purchased titles, and #AudiobookShelf that can help me organize and listen to them - even when I'm on the road. Recently I've discovered that OpenAudible comes in a #containerized version, which is right up my alley - I could run it on my Synology NAS, access it from anywhere and not worry about files filling up my laptop or desktop system. Now here's the amusing part: sure the OpenAudible guys have provided a "containerized" version, but it's done in all the wrong ways: it's still running their Java application, but wrapped in an HTTP-enabled remote desktop client that accesses a Linux desktop, which is also running in the container. There's even an SSH server running there. Guys, while your application is most excellent, you have many things to learn about containers - full fat VM-like containers is not how you do it.

  9. I like #Audible, but I also prefer to have my audiobooks on my own storage. Luckily there is #OpenAudible that can download my legally purchased titles, and #AudiobookShelf that can help me organize and listen to them - even when I'm on the road. Recently I've discovered that OpenAudible comes in a #containerized version, which is right up my alley - I could run it on my Synology NAS, access it from anywhere and not worry about files filling up my laptop or desktop system. Now here's the amusing part: sure the OpenAudible guys have provided a "containerized" version, but it's done in all the wrong ways: it's still running their Java application, but wrapped in an HTTP-enabled remote desktop client that accesses a Linux desktop, which is also running in the container. There's even an SSH server running there. Guys, while your application is most excellent, you have many things to learn about containers - full fat VM-like containers is not how you do it.

  10. I like #Audible, but I also prefer to have my audiobooks on my own storage. Luckily there is #OpenAudible that can download my legally purchased titles, and #AudiobookShelf that can help me organize and listen to them - even when I'm on the road. Recently I've discovered that OpenAudible comes in a #containerized version, which is right up my alley - I could run it on my Synology NAS, access it from anywhere and not worry about files filling up my laptop or desktop system. Now here's the amusing part: sure the OpenAudible guys have provided a "containerized" version, but it's done in all the wrong ways: it's still running their Java application, but wrapped in an HTTP-enabled remote desktop client that accesses a Linux desktop, which is also running in the container. There's even an SSH server running there. Guys, while your application is most excellent, you have many things to learn about containers - full fat VM-like containers is not how you do it.

  11. Creative means to address #RogueApps that demand your #FullAddressbook to use the app is just an #RFE away from being #containerized to emulate #YourWholeAdressbook to said #RogueApps that demand this access to work.

    #TakeBackControl via #IEEE & #IETF 🧐

    ⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇

    infosec.exchange/@infosec_jcp/

  12. Creative means to address #RogueApps that demand your #FullAddressbook to use the app is just an #RFE away from being #containerized to emulate #YourWholeAdressbook to said #RogueApps that demand this access to work.

    #TakeBackControl via #IEEE & #IETF 🧐

    ⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇

    infosec.exchange/@infosec_jcp/

  13. Creative means to address #RogueApps that demand your #FullAddressbook to use the app is just an #RFE away from being #containerized to emulate #YourWholeAdressbook to said #RogueApps that demand this access to work.

    #TakeBackControl via #IEEE & #IETF 🧐

    ⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇

    infosec.exchange/@infosec_jcp/

  14. Creative means to address #RogueApps that demand your #FullAddressbook to use the app is just an #RFE away from being #containerized to emulate #YourWholeAdressbook to said #RogueApps that demand this access to work.

    #TakeBackControl via #IEEE & #IETF 🧐

    ⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇

    infosec.exchange/@infosec_jcp/

  15. Creative means to address #RogueApps that demand your #FullAddressbook to use the app is just an #RFE away from being #containerized to emulate #YourWholeAdressbook to said #RogueApps that demand this access to work.

    #TakeBackControl via #IEEE & #IETF 🧐

    ⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇⚠️👇

    infosec.exchange/@infosec_jcp/

  16. @patrickcmiller I tend to shy away from #containerized images for sensitive #Production services (Financial etc) that don't have to #scale up/down too quickly. Great for segregated Dev/Test/UAT etc. environments, but *still* not quite as #secure as good ol' #VMs/Bare metal. Of course, any deployment can have flaws...

  17. @patrickcmiller I tend to shy away from #containerized images for sensitive #Production services (Financial etc) that don't have to #scale up/down too quickly. Great for segregated Dev/Test/UAT etc. environments, but *still* not quite as #secure as good ol' #VMs/Bare metal. Of course, any deployment can have flaws...

  18. @patrickcmiller I tend to shy away from #containerized images for sensitive #Production services (Financial etc) that don't have to #scale up/down too quickly. Great for segregated Dev/Test/UAT etc. environments, but *still* not quite as #secure as good ol' #VMs/Bare metal. Of course, any deployment can have flaws...

  19. @patrickcmiller I tend to shy away from #containerized images for sensitive #Production services (Financial etc) that don't have to #scale up/down too quickly. Great for segregated Dev/Test/UAT etc. environments, but *still* not quite as #secure as good ol' #VMs/Bare metal. Of course, any deployment can have flaws...

  20. @patrickcmiller I tend to shy away from #containerized images for sensitive #Production services (Financial etc) that don't have to #scale up/down too quickly. Great for segregated Dev/Test/UAT etc. environments, but *still* not quite as #secure as good ol' #VMs/Bare metal. Of course, any deployment can have flaws...

  21. Over where I work, the dev model is moving from a shared #dev server to #containerized #docker instances in #redhat.
    Q: how to ease the learning curve?

  22. Over where I work, the dev model is moving from a shared #dev server to #containerized #docker instances in #redhat.
    Q: how to ease the learning curve?

  23. Over where I work, the dev model is moving from a shared #dev server to #containerized #docker instances in #redhat.
    Q: how to ease the learning curve?

  24. @Charadon For something like a workstation, do you need a LTS release any more?

    I would think development or other could keep your tool chains and critical environments stable and at arms length from whatever OS you happen to use underneath, at least for most use-cases I can imagine.

  25. @Charadon For something like a workstation, do you need a LTS release any more?

    I would think #containerized development or other #virtualization could keep your tool chains and critical environments stable and at arms length from whatever OS you happen to use underneath, at least for most use-cases I can imagine.