2026-09-15 20:33 UTC
it is new day, post zoo visit (got to see some painted doggies chilling out), now need to investigate this again. i still don't understand why, exactly, it's mad about the placement of the file but i'm going to try and run a purely local instance directly first w/o building anything via docker and see if it works properly. if it doesn't work with the file location as specified there's something a lil' off but if it does, i need to figure out why the docker build chain doesn't let this happen as i expect it to.
Replies (1)
-
@senil@gts.social.senil.me 2026-09-15 20:45
ok so it IS fine with the same nicolium.json file that exists in the docker container, so it's either some permissions thing (i can't imagine why? i'll add a chown to it though, to be sure) or something weird is going on. the folder structure matches what i've extracted on my desktop once i get to the appropriate level in the container, so idk what's going on there. i'll poke around with it, but it does confirm to me that the nicolium.json file that should be loaded onto this instance is valid, it's just not being loaded right as far as i can tell.