Digaumspider

I'm trying to install this docker from scratch (first time using Loki or Grafana) and even after following the instructions and uploading the yaml file, the docker doesn't start. Upon checking the logs, here's what I'm getting: mkdir /loki/chunks: permission denied error creating object client github.com/grafana/loki/pkg/storage.(*store).chunkClientForPeriod /src/loki/pkg/storage/store.go:187 github.com/grafana/loki/pkg/storage.(*store).init /src/loki/pkg/storage/store.go:155 github.com/grafana/loki/pkg/storage.NewStore /src/loki/pkg/storage/store.go:147 github.com/grafana/loki/pkg/loki.(*Loki).initStore /src/loki/pkg/loki/modules.go:656 github.com/grafana/dskit/modules.(*Manager).initModule /src/loki/vendor/github.com/grafana/dskit/modules/modules.go:120 github.com/grafana/dskit/modules.(*Manager).InitModuleServices /src/loki/vendor/github.com/grafana/dskit/modules/modules.go:92 github.com/grafana/loki/pkg/loki.(*Loki).Run /src/loki/pkg/loki/loki.go:458 main.main /src/loki/cmd/loki/main.go:110 runtime.main /usr/local/go/src/runtime/proc.go:250 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1598 error initialising module: store github.com/grafana/dskit/modules.(*Manager).initModule /src/loki/vendor/github.com/grafana/dskit/modules/modules.go:122 github.com/grafana/dskit/modules.(*Manager).InitModuleServices /src/loki/vendor/github.com/grafana/dskit/modules/modules.go:92 github.com/grafana/loki/pkg/loki.(*Loki).Run /src/loki/pkg/loki/loki.go:458 main.main /src/loki/cmd/loki/main.go:110 runtime.main /usr/local/go/src/runtime/proc.go:250 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1598 level=warn ts=2023-12-28T04:57:45.836853066Z caller=loki.go:286 msg="per-tenant timeout not configured, using default engine timeout (\"5m0s\"). This behavior will change in the next major to always use the default per-tenant timeout (\"5m\")." level=info ts=2023-12-28T04:57:45.838308866Z caller=main.go:108 msg="Starting Loki" version="(version=2.8.7, branch=HEAD, revision=1dfdc432c)" level=info ts=2023-12-28T04:57:45.838613841Z caller=modules.go:895 msg="Ruler storage is not configured; ruler will not be started." level=info ts=2023-12-28T04:57:45.839282779Z caller=server.go:334 http=[::]:3100 grpc=[::]:9095 msg="server listening on addresses" level=warn ts=2023-12-28T04:57:45.840004236Z caller=cache.go:114 msg="fifocache config is deprecated. use embedded-cache instead" level=warn ts=2023-12-28T04:57:45.841471312Z caller=experimental.go:20 msg="experimental feature in use" feature="In-memory (FIFO) cache - chunksembedded-cache" level=error ts=2023-12-28T04:57:45.842359094Z caller=log.go:171 msg="error running loki" err="mkdir /loki/chunks: permission denied\nerror creating object client\ngithub.com/grafana/loki/pkg/storage.(*store).chunkClientForPeriod\n\t/src/loki/pkg/storage/store.go:187\ngithub.com/grafana/loki/pkg/storage.(*store).init\n\t/src/loki/pkg/storage/store.go:155\ngithub.com/grafana/loki/pkg/storage.NewStore\n\t/src/loki/pkg/storage/store.go:147\ngithub.com/grafana/loki/pkg/loki.(*Loki).initStore\n\t/src/loki/pkg/loki/modules.go:656\ngithub.com/grafana/dskit/modules.(*Manager).initModule\n\t/src/loki/vendor/github.com/grafana/dskit/modules/modules.go:120\ngithub.com/grafana/dskit/modules.(*Manager).InitModuleServices\n\t/src/loki/vendor/github.com/grafana/dskit/modules/modules.go:92\ngithub.com/grafana/loki/pkg/loki.(*Loki).Run\n\t/src/loki/pkg/loki/loki.go:458\nmain.main\n\t/src/loki/cmd/loki/main.go:110\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598\nerror initialising module: store\ngithub.com/grafana/dskit/modules.(*Manager).initModule\n\t/src/loki/vendor/github.com/grafana/dskit/modules/modules.go:122\ngithub.com/grafana/dskit/modules.(*Manager).InitModuleServices\n\t/src/loki/vendor/github.com/grafana/dskit/modules/modules.go:92\ngithub.com/grafana/loki/pkg/loki.(*Loki).Run\n\t/src/loki/pkg/loki/loki.go:458\nmain.main\n\t/src/loki/cmd/loki/main.go:110\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598" After manually creating the directories, it started running, but I'd like to know how to avoid this in the future. What's that about 10001:10001 you mentioned above? Is this a permission that needs to be applied to the docker container or the directories themselves? How would I go about doing that? I only know chmod commands or chown, but I have no idea what 10001 means. Thanks!

Second this. Tried installing it and I'm getting a lot of errors. Then tried finding the guide on how to get it up and running properly, but it's either this topic or the official Graylog website (which doesn't include details on the unraid docker container config, for obvious reasons). Any other recommendations? Thank you!

I guess I'll wait for more responses here, then.

Hello, @SidM. Seems like you're also on the same boat as me, and simply want to change to this container without losing any of your previous configs. Were you able to do so by simply modifying the source of the docker containers above or did you have to change anything else? Thanks!

Hello @Kilrah. I've been using Linuxrepository's Nextcloud container for a good month now, but just got stuck on the mp4 thumbnail generation issue and doing a research here in the forums, I came across your topic. This seems to fit the bill for me, but would it be possible to not lose my existing nextcloud config (users, passwords, files, permissions, apps, etc) and simply remove the existing linuxrepository container and install yours (by using all the same settings in the docker container as the ones uses on Linuxrepository's container)? Or would I have to get rid of everything and start from scratch (removing all my previous nextcloud appdata along with it)? Thanks!

Is there any way at all to check the Unraid built-in Wireguard for the logs to see if someone I haven't authorized has been accessing my network via wireguard? In short, my FW has passed multiple connections from outside that didn't come from me, and now I want to check my wireguard and make sure these were just attempts and wireguard shut them down or if they passed for some reason. Thanks.

I know it's been a while, but I'm revisiting this and was wondering if you guys had any recommendations. Thanks!

Have you managed to get your other containers to route through this one successfully? If so, any guides I can follow to achieve it from my end as well? Thanks!

Anyone tried installing this Docker image recently in Unraid? (nordlynx) Here's what happens on my Unraid: I click the Install button on the apps page, then get taken to the configuration page, then after making sure it's all good, I click Done and, instead of seeing this show up running under my docker images, I'm taken back to the apps page, and no nordlynx shows up there at all along with the rest of my docker images. Is this expected? Should I be changing anything else in the settings before clicking Done? Thanks

Thanks. I wasn't aware of that. Now I know. I'll mark Jorge's response as the solution, though, as he allowed me to rebuild the cache and bring it back to a functional state again, to the point where I can use the docker solution normally again. Also, on the documentation: For what is worth, I tried following the steps there, but if you scroll up and take a look at my screenshot, the official documentation conflicts directly with the solution to the problem, so I thought it best to double (and triple) check here first before going ahead. Might be helpful to folks in the future if the documentation is updated to reflect the correct steps to be taken. Again, thank you for the help.

I've followed the steps to format (and fully erase the content) of the pool of 2x SSD drives in btrfs (by changing to encrypted and then back to normal). Then, I created a new docker.img (recommended by the backup restoration tool), and started the docker service. I, then, restored the appdata from a back from last week, which took several hours. Even though I can see over 100GB of data (expected) in the appdata folder, including all my older docker applications, none of them show up under my docker area at all. So the data is physically there, but docker doesn't recognize them as it should... Since this is my first time restoring the data (I'm using the Backup/Restore appdata tool under settings), am I doing something wrong here? Diagnostics are attached, in case they're needed. I'll also be happy to post screenshots, if it helps. Thank you. unraid-server-diagnostics-20230301-1733.zip

Here you go: [1/7] checking root items [2/7] checking extents backref 1565130752 root 18446612693123346832 not referenced back 0x29cb4a0 tree backref 1565130752 root 2 not found in extent tree incorrect global backref count on 1565130752 found 2 wanted 1 backpointer mismatch on [1565130752 16384] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdf1 UUID: e0fd7e5a-50c1-410a-89e6-f41a0c634d63 found 149333053440 bytes used, error(s) found total csum bytes: 145464004 total tree bytes: 377913344 total fs tree bytes: 171819008 total extent tree bytes: 34390016 btree space waste bytes: 57082664 file data blocks allocated: 3987076739072 referenced 145612578816

Thank you again for your patience, and I apologize for asking it again, but just trying to make sure that my data won't be wrecked, so please bear with me. I've clicked the link you posted, and it took me straight to that part of the post. I've got BTRFS running my cache, so in order to run said "Check Filesystem", what exactly should I do? I went over the instructions posted, but couldn't find anything that would indicate that I should bring the cache running BTRFS into maintenance mode and then run any different commands. Here's what I'm reading when I click the link you shared: Thank you once again.

I'm sorry, did I misunderstand the paragraph below? I'm just trying to make sure I'm not going to destroy the data there by double checking. What am I missing? Thanks again.

Attaching the logs here after a successful reboot. Also, the document you linked to has a piece of info that conflicts with my case (SS below). Here's what I see (it's telling me to start it in maintenance mode, although the instructions are clear that I should NEVER run this in maintenance mode for BTRFS filesystems): Any ideas? Thanks unraid-server-diagnostics-20230227-2138 (1).zip