• 0 Posts
  • 26 Comments
Joined 1 month ago
cake
Cake day: November 21st, 2025

help-circle
  • Never used containers on synology.

    Seems weird to me that there’s an AIO container that seems to contain other containers, but anyway I guess thats a synology thing.

    Maybe this is obvious to everyone else but… all those containers are “starting” because theyre waiting for one other container to finish “starting” before starting up themselves.

    I agree that the redis warnings seem benign.

    Weird that nextcloud is waiting for a db but postures says its ready.

    Is the 404 in the master container logs from you trying to access the instance in your browser?

    I assume there’s some kind of compose.yaml as part of the AIO project you’re installing which will reveal which containers “depends_on” which other containers so you could figure out which one is blocking you.



  • I’m not a windows user and haven’t used jackett.

    This is the relevant issue on github: https://github.com/Jackett/Jackett/issues/16352

    The TLDR is, it’s a false positive.

    The change they think triggered it is that there’s an “if” statement to detect the operating system and if so it moves some files.

    They’ve submitted the file to some antivirus vendors so they can improve their false positive detection system. I wouldn’t expect a result on that front but who knows.

    Nothing is a surety in life but:

    • there’s a lot of transparency around this issue
    • lots of people have reviewed the code regarding this specific issue
    • it’s a long standing project with good community support and no recent shady changes to maintainers
    • false positives do happen

    You need to make your own decision but IMO, “very low” risk.


  • Yeah, I hate facebook too, but sometimes you just have to acknowledge that flying the FOSS flag is not your primary objective. Like someone else said, if you have half the people on whatsapp, you’ll get much less than that with anything else.

    I occasionally dream of having a better “community” in my suburb but basically, I just have zero available effort to invest in that. Like I’m not working today and looking forward to spending the afternoon in my pyjamas fiddling around at home. If I feel super motivated and energetic later I might take the kids somewhere. If there were a community thing scheduled I just… wouldn’t feel like going.

    I think the best form of community I can manage is simply having a few people’s numbers in my phone and telling them when something happens “Hey Barb, just letting you know the neighbours car got broken into last night, hows things down your end?”



  • Containers have layers. So if you create an instance of a syncthing container whoever built that container would have started with some other container. Alpine linux is a very popular base layer, just used as an example in this discussion.

    When you download an image, all the layers underlying the application that you actually wanted, will only be as fresh as the last time the maintainer built that image. So if there were a bug in the alpine base, that might have been fixed in alpine, but wouldn’t by pushed through to whatever you downloaded.





  • fizzle@quokk.autoMicroblog Memes@lemmy.worldmozilla rn
    link
    fedilink
    English
    arrow-up
    54
    arrow-down
    3
    ·
    11 days ago

    It’s ok buddy.

    I defended mozilla for the longest time. Trying to see the underlying motive for every dumb decision, challenging others to at least acknowledge their strategy.

    This latest brain fart from the new CEO is the end of that though.

    It’s fine to keep defending them, but it would also be fine to acknowledge that mozilla is actively alienating Firefox’ loyal following.


  • This is me.

    For example, /srv/docker/synching contains:

    compose.yml .env ./Sync

    That last one is a directory bound to the container which contains all my sync folders.

    Occasionally it makes more sense to put the mounted folder in /srv like /srv/photos is mounted by /srv/docker/photoprism/compose.yml

    However, thats a rarity. Things mostly accessed by a single compose stack are kept alongside the other files for that stack.