kayront: Try the latest release

LeftWing: i added it to /data/chroot/dev-2020Q4-x86_64//home/pbulk/build/databases/prometheus/work/src/github.com/prometheus/prometheus/vendor/github.com/docker/docker/client/client.go and tried bmake again, but it's still the same. then tried again with bmake clean, bmake extract, made the change, and bmake, but still the same. did I miss something obvious?

kayront: I don't think you should have to edit any files

I meant the latest release of Prometheus

2.23.0 has that problem, but I believe 2.24.1 does not

but but .. i'm almost done making everything tidy with 2020Q4 and it's looking so shiny!

after months of neglect :o

i'm using a delegated dataset in a zone, and under that there will be an encrypted filesystem. do we have any good smf stuff for having services that will store their data under the encrypted filesystem depend on a pseudo-service that waits until the filesystem is made available by entering the decryption key?

or did I just volunteer my sunday morning

:D

(or some other way to achieve this, i believe the way above is what makes the most sense on an illumos system but feel free to correct/improve the idea)

kayront: oh sorry, looks like I fixed prometheus in trunk but forgot to backport to 2020Q4: NetBSD/pkgsrc f45394f

jperkin: ah, it's solaris and not illumos. building again :)

===> Building binary package for prometheus-2.23.0

BUILD ALL THE THINGS!

well it'll need to be illumos to support the illumos target, though really upstream should just change the whole thing to !windows or something, individually listing OS is silly

jperkin: once i thought it was an accident, but it's happened again: it seems that static routes are not picked up by reprovision

also customer_metadata

20201022T155042Z

i'm getting a ton of errors related to libleveldb trying to pip3 install plyvel .. try pkgin in leveldb, then pip3 install plyvel, does it also error out ?

ld: fatal: relocations remain against allocatable but non-writable sections

papertigers any idea if/when the newer ubuntu images will be published?

does terraform with with vanilla smartos at all?

sjorge: lx or HVM?

And I was just talking about taking a week to work through a bunch of images. Maybe that will be this weeks task

lx

kayront : I don't think, that vanilla SmartOS has an API, that terraform could interact with

there's a provider at least that says it uses SSH: github.com/john-terrell/terraform-provider-smartos

oh - I didn't knew that

sounds a little bit like ansible that way :-)

indeed :O

sjorge: there's the beta image I posted. But we can try to get something more proper this week. I will focus on images

The beta image was

mostly working OK for me

I don't recall any new issues compared to the latest published one

currently having an issue with byhve zones where there disk usage keeps growing unbounded, they are based off the certified ubuntu 18 zvols, after some months (or less due to disk activity) they eventually refer to move disk than the original quota allows causing an outage as zfs sets the fs to read only.

is there anyway to mark unused space to be freed by zfs? currently have a 64G volume with 3G of actual content refering to 65G