[06:45] <Guest38> Hi folks, if we launch an ubuntu server lts 20.4 container, install the necessary softwares, will we be able to later on upload to somewhere like docker hub/github and the download and run this. "golden" container that has all the necessary softwares already installed on another machine?
[08:05] <frickler> Guest38: well the usual way to do this would be to create a Dockerfile that describes all the customization steps, but it should also be able to do that manually. in the end one could consider that to be one of the key features of docker even
[08:10] <Guest38> frickler but hmmm.. i wan to download the container and run on another machine which is a synology nas using synology's docker feature.
[15:19] <infectedserver> Hi, my copy of Ubuntu server has been infected by Monero mining malware. I am of re-installing, but I am trying to do some investigations to understand the level of compromise.
[15:20] <infectedserver> One thing I noticed is that the SSH host key has changed. Why would malware authors do this?
[15:20] <infectedserver> Another thing I noticed: a hidden file name "/usr/sbin/.lib1", that repeatedly runs a binary called "systemd" in the same binary, but systemd is actually a monero miner
[15:33] <sdeziel> infectedserver: that's a bit stupid for them to change the SSH host key(s) as that makes it pretty noticeable ...
[15:37] <infectedserver> well, 100% CPU usage is also pretty notiecable
[15:50] <shubjero> coreycb: Is juju a premium ubuntu feature? Is there a documented path to migrate from openstack deployments using ubuntu apt to juju?
[15:52] <coreycb> shubjero: no juju is open source and available for anyone to use
[15:52] <coreycb> shubjero: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/
[15:54] <coreycb> shubjero: btw we're working on bisecting to narrow in on the offending commit for the bug that's affecting you
[15:54] <shubjero> coreycb: yeah I just updated that ticket, thanks again for your efforts. I gained a lot of grey hair on this upgrade to Ussuri haha
[21:06] <pcfreak30> Hello, I have a question. Im trying to install 18.04 ontop of lvm which is on a raid 0 (i know raid 0 is bad). the ncursus installer is wanting a boot disk after i mounted one lv to / and another to /boot. what am i missing
[21:20] <sdeziel> pcfreak30: I don't quite remember if grub has all it needs to boot from a FS stored in a LV on top of raid0. IIRC I used to have a similar setup except I was using raid 1 and /boot was in the same LV as / (ext4).
[21:21] <pcfreak30> sdeziel: im switching to the debian installer to see if it will help. im reading a lot of b*tching on ubuntus new "live" install system
[21:21] <pcfreak30> and i was trying to put boot on / too but it wouldnt let me
[22:28] <pcfreak30> sdeziel: the debian installer allowed my disk setup but i could not seen to get grub to install due to a disk filter write error when i chrooted manually.
[22:29] <pcfreak30> its forcing it to be a physical disk and that would be wasting a disk unless i can use raid with a partition
[23:13] <pcfreak30> Any reason a partition cannot be set as a boot disk?? I have 1 partition set as /boot and the rest of the disk as raid, and the other disks raid as a whole (no partition table).
[23:13] <pcfreak30> tried on 18.04 and 20
[23:15] <mwhudson> you need to partition the disk to be able to use it as a boot disk
[23:16] <mwhudson> and by boot disk that means "somewhere to put grub", i.e. an ESP for uefi or space at the front of the disk for legacy boot
[23:21] <pcfreak30> " you need to partition the disk to be able to use it as a boot disk" i created a 2Gb partition as 1, and a linux raid partition as 2. despite that it blocked making it a "boot" disk even though it was set to mount at /boot
[23:21] <mwhudson> pcfreak30: uefi or legacy boot?
[23:22] <mwhudson> pcfreak30: also /boot is nothing to do with this (confusingly) you can stop talking about that for now
[23:22] <pcfreak30> right now im assuming legacy. havent tried to do uefi explicitly
[23:23] <mwhudson> was the disk partitioned before you started the installer or did you create the partitions in the installer?
[23:24] <pcfreak30> i created them in a shell the reset the partitioner to refresh it but it was being restritive.
[23:25] <pcfreak30> because*
[23:25] <mwhudson> oh 
[23:25] <pcfreak30> just rebooted now b/c it was acting up
[23:25] <mwhudson> well in this case you will have better luck if you reformat the disk in the installer
[23:25] <pcfreak30> But I now have a gpt table with 1 partition in all disdks but the one that has a 2gb partition for the boot drive
[23:25] <pcfreak30> gpt*
[23:26] <pcfreak30> havent done any formatting yet
[23:26] <mwhudson> i mean create the partitions in the installer
[23:26] <pcfreak30> it just seems to be a bit anal about some stuff so been doing it manual 
[23:38] <sdeziel> pcfreak30: if you mostly want a raid 0, you can probably partition both disks with a single partition covering 1MB till the end, stripe them, put LVM on top and install grub into both MBRs
[23:39] <sdeziel> pcfreak30: having a partition will make the 1st MB usable by grub which you might as well install into each disks, just in case
[23:41] <pcfreak30> im on mbr not uefi btw
[23:50] <pcfreak30> sdeziel: doing everything in the installer sort of works. i create the boot partition 1st but then in building the raid it locks it out as a raid member -_-
[23:50] <pcfreak30> so i have 3 and not 4 to use
[23:52] <sdeziel> pcfreak30: with LVM and raid (0 or whatever) under it, I'd aim for a single partition unless you want different raid level to back multiple PVs
[23:53] <pcfreak30> right now i had it create the boot 1st, THEn i created 1 partition under each. it just refuses to allow the partition i created for raid on the boot drive!
[23:53] <pcfreak30> I could add it after install but thats just painful
[23:54] <pcfreak30> and yes it has a 1 mb partition created
[23:57] <pcfreak30> sdeziel: https://imgur.com/a/mHCAI2E
[23:59] <sdeziel> pcfreak30: as you said, this seems to be a GPT partition (IIRC this is when the bios_grub part is needed)