[04:06] good morning [07:03] good morning [10:18] good morning [11:11] good evening [11:11] Lets discuss Ubuntu now! [11:11] Any good light weight Ubuntu docker images? [11:12] Or should i do Debian buster or AlpineLinux? [11:24] I don;t really do Docker (might try it though) [11:25] What is it? [11:30] vmguy23m: A container management infrasturuce [11:30] I don't really know about containers [11:30] like LXC but multiplatform and smarter with its own repo [11:30] LXC on steroids without the roid rage === vmguy23m is now known as [VMGuy23] [11:40] <[VMGuy23]> i DON'T KNOW WHAT lxc IS [11:41] <[VMGuy23]> Whoops, sorry about caps [11:42] [VMGuy23]: It's a linux thing [11:42] linux containers supported by the kernel [11:47] the thinking is that instead of booting up and running entire VMs which consume more resources to bring up a whole other kernel and OS to manage, just load up the bare essentials to support the service you want to run linked against the host's kernel [11:47] personally i'll stick to VMs though (: don't get the container hype [11:47] it probably suits web apps well? not sure [11:48] <[VMGuy23]> I have 4 VMs currently, none running [11:49] daftykins: Docker has an extra layer though, well, depending on the OS,. [11:49] [VMGuy23]: But you are VM guy [11:49] you should have at least 23 of them [11:49] yeah this strikes me as false advertising ;) [11:49] :P [11:50] <[VMGuy23]> I only have 185GB total disk space, 23 is a bit too much [11:50] <[VMGuy23]> If i had 2 or 3 it could be 2-3 [11:50] not if they are all server installs ;) [11:50] <[VMGuy23]> Got to go, be back [11:53] gg [12:33] <[VMGuy23]> I'm back [12:33] WB VM GUy 23 [12:34] <[VMGuy23]> ? [12:35] WB = Welcome Back [12:35] <[VMGuy23]> Oh, makes sense [12:40] <3 [12:40] Lets pal team it up [12:40] Discuss [12:43] <[VMGuy23]> wyoung: I like Rythmbox but GNOME Music is good [12:44] Lets discuss [12:44] It is good [12:44] but I can't tell you how to use it here, we need to switch back to #ubuntu for support. [12:45] you sure can discuss it here [12:45] <[VMGuy23]> I've had a bad experience (crashes, freezes) with a lot of Linux software, from my time on Raspberry Pi (started on 3B+, then got 4) [12:46] lotuspsychje: but up tp a point, if you offer support then you need to switch [12:47] [VMGuy23]: You get what you pay for., [12:48] wyoung: you can discuss supporting software in here aswell, things that dont really fot into #ubuntu for example [12:48] *fit [12:49] oh? [12:49] What if it does fit into Ubuntu? [12:49] Will I be asked to leave and goto Ubuntu instead? [12:50] wyoung: if you seek ubuntu support join #ubuntu [12:50] * pauljw wonders why we bother with a channel topic [12:52] its really not so hard to divide support questions from discussions [12:53] I am just asking because I want to know which channel is more anal about the division, [13:00] wyoung: how long have you been on IRC? [13:01] Maik: Too long, which is why I asked [13:01] then you'd know by know how things work [13:01] I do, ops are usually nazis, fascists and hypocrites. [13:02] That trend needs to change though [13:03] careful what you say because of the CoC and channel guidlines that apply in all the buntu channels [13:03] Maik: I understand, the secret police will get me [13:04] Maik: The CoC needs to apply to ops too [13:05] of course [13:06] I have never seen that enforced [13:07] Although talking about it here is within topic right? [13:07] depends on how someone behaves, saying ops are usually nazis, fascists and hypocrites can get you banned [13:08] wyoung: read the topic and you know [13:08] Maik: That is my experience on ops in IRC, are you saying I am wrong? [13:08] sigh [13:08] What channel did you come from? [13:08] jeremy31: Pyhon [13:08] Python* [13:09] That isn't covered by Ubuntu COC [13:09] Including the dicuss channel? [13:09] yes [13:10] all ubuntu related channels [13:10] wyoung: Ubuntu CoC covers any channel with #ubuntu [13:10] OK [13:10] wow and he's been on irc for a long time.... [13:10] I have been [13:10] On channels that don't start with #ubuntu [13:11] <[VMGuy23]> I've been on IRC for 3 weeks I think [13:11] I was on some channels back in the late 1990s [13:11] jeremy31: early 1990s here [13:11] We didn't have internet here until late 1995 [13:16] <[VMGuy23]> Windows NT Server existed before 1995 I think [13:44] correct [13:45] 95's desktop UI was ported over from NT [13:46] <[VMGuy23]> NT originally had Program Manager [13:49] <[VMGuy23]> I think they got the design update at a similar time [20:29] Hi, I am looking for an answer, and sorry if it is a sensitive topic, but I am honestly confused and lost. I used to be an Ubuntu user back in the Ubuntu 6.06 days, and now find myself with technologies such as snap and flatpak, and feel like I've dropped off somewhere. [20:30] When I used Ubuntu, we used /opt for self-contained applications, or /usr/local. Does this relate to flatpak/snap? [20:31] I sincerely don't know, because I usually thought that self-contained applications were to be installed in /opt, and now this snap thing seems to go on an entirely different direction. [20:31] glamboy: flatpac and snap are similat - ubuntu adheres to snap packing for IOT containerization, Life on the desktop can go on without snaps :) [20:31] similar* [20:31] glamboy: high-level, snaps and flatpaks carry all dependencies for the application to run. This makes it possible to deploy the very same snap/flatpak on different distro's versions, without the need to backport and rebuild against a specific distribution version [20:32] Ok. But if I were to, say, make a .deb package with a folder structure in /opt and add static libraries, would it be considered ok in a backports/untrusted sort of repository or a PPA? [20:33] Just thinking, because I started building something using a custom folder structure, and my idea was to set it up in /opt with its static libraries, etc. [20:34] Would it be ok to make a .deb with this type of structure, or am I better off learning these new technologies? [20:36] it is OK to build and/or deploy actual packages [20:37] in your PPAs you can build them for whichever distro versions you want. The advantage of snap/flatpak is would would only need to build ONE, for all versions. [20:38] Ok, so it's a matter of safely keeping software across versions, not just self-containment. [20:39] both, probably. In general, in a snap/flatpak you cannot change the *system*. But you would do better to study them before trying [20:39] Just have to maintain one version for all supported Ubuntu versions [20:40] In flatpak, my software would always work even in the case of an upgrade, whereas a self-contained .deb in /opt would have to be rebuilt with every new version. [20:40] snap/flatpak( [20:41] I am partial to the self-contained .deb in /opt route, because it's uniform with the rest of the packages that the distro brings, and because it's so easy to maintain, just a few more checks around copying the file to /opt/ [20:42] But this whole cross-upgrade dimension seems interesting as well.