RhondaSandTits

@RhondaSandTits@lemmy.sdf.org

• ⁨Comment⁩ on ⁨Need help with searxng docker compose⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  Glad to see you got it working. One thing to add that you might find useful:

  it shows 20054:8080 for a very short period when I start the stack and then disappeared

  This is an indication that the container has stopped. Because you have restart: unless-stopped set, the container is stuck in a bootloop so portainer will always show a state of either starting or running. Docker container automatically stop when the application inside the container has exited or completed… Often because the application has encountered an error.

  Some more information that may or may not be useful:

  A good example of a container stopped because the application has finished is the Cross-seed container that people use to cross reference their torrents seeding in their bittorrent client with torrents available on other torrent trackers. In this case, the application runs a search on each tracker, downloads the files and once the search is done the application exits and then the docker container will stop.

• ⁨Comment⁩ on ⁨Plex is locking remote streaming behind a subscription in April⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  The reality is that we need more resources to continue putting forth the best personal media experience

  How stupid do they think we are?