[BUG] "s6-rc-init: fatal: unable to supervise service directories in /run/s6-rc/servicedirs: Broken pipe" when starting container

[scottdrmyers]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I had watchtower update the container automatically and saw that it was not running. I then re-deployed as a stack and still get the same error. This has been working for months with no changes except automatically container upgrades.

I have 15 other containers running without issues with no conflicting ports.

Expected Behavior

Container should start normally.

Steps To Reproduce

Nothing special here. Just simply try to deploy the container. As a test, I deployed on a second docker host, same results.

Environment

- OS: Ubuntu 22.04
- How docker service was installed: https://docs.docker.com/engine/install/ubuntu/ - Using apt repo. Stays current with sudo apt update && sudo apt upgrade commands.

CPU architecture

x86-64

Docker creation

`version: "2.1"
services:
  tautulli:
    image: lscr.io/linuxserver/tautulli:latest
    container_name: tautulli
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Halifax
    volumes:
      - /home/minipc/tautulli/config:/config
    ports:
      - 48181:8181
    restart: always`

Container logs

`2024-01-12T03:03:16.755837697Z s6-rc-init: fatal: unable to supervise service directories in /run/s6-rc/servicedirs: Broken pipe`

Nothing else in the log unless there is a specific place to look for more info.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[scottdrmyers]

Note: I deployed the following as a test:

version: '3'
services:
  tautulli:
    image: **ghcr.io/tautulli/tautulli:latest**
    container_name: tautulli
    restart: always
    volumes:
      - /home/minipc/tautulli/config:/config
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Halifax
    ports:
      - 48181:8181

This container works correctly. At the end of the day it's not a huge deal, but at least I'm up and running. Seem the container hosted here is hosed maybe?

[aptalca]

Lscr and ghcr endpoints are exactly the same at the moment as lscr points to (forwards to) ghcr. You likely had a malformed image download the first time around. A repull probably fixed it.

[scottdrmyers]

Lscr and ghcr endpoints are exactly the same at the moment as lscr points to (forwards to) ghcr. You likely had a malformed image download the first time around. A repull probably fixed it.

Not the case. I am able to reproduce this on two different host machines. I just tried it again, deleted the stack and images, repulled and redployed, same error. If I delete the stack and images and switch to ghcr.io, it deploys correctly.

One machine has never had this deployed and experienced the issue.

Either way, I'm moving forward with the ghcr.io, something is either happening in the forwarding process or somewhere else along the line.

[aptalca]

Lscr does not host any images. It's just a forwarding service. It currently forwards to ghcr, which is where the images are downloaded from.

https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter

[aptalca]

Ah well, it was just brought to my attention that the ghcr address you used is not our image. So you're comparing apples to oranges

[scottdrmyers]

Ah well, it was just brought to my attention that the ghcr address you used is not our image. So you're comparing apples to oranges

I'm not sure where the confusion is here

lscr.io/linuxserver/tautulli:latest -- Does not work.
ghcr.io/tautulli/tautulli:latest -- Works

You indicated that is is just a forwarding service from lscr.io to ghcr.io. You said this was the same above. Now it's not?

Now this actually proves that lscr.io/linuxserver/tautulli:latest is the issue. This is what I am indicating is not working. I used ghcr.io/tautulli/tautulli:latest as a test in my reply above and confirmed it works.

So if lscr.io/linuxserver/tautulli:latest does not work, wouldn't that indicate there is an issue with lscr.io/linuxserver/tautulli:latest ?

What am I missing here?

[j0nnymoe]

ghcr.io/tautulli/tautulli:latest is not our image so it's not comparing like for like.

If you want to test our image via ghcr.io, do ghcr.io/linuxserver/tautulli:latest instead.

[thespad]

You're pulling two completely different images so you can't compare them in any meaningful way.

Our image is fine and works:

$ docker run -d --rm --name=tau --tmpfs /config lscr.io/linuxserver/tautulli:latest && docker logs -f tau
Unable to find image 'lscr.io/linuxserver/tautulli:latest' locally
latest: Pulling from linuxserver/tautulli
b36d7c4439ae: Already exists 
07a0e16f7be1: Already exists 
44b4c95fd317: Already exists 
ab4a4bec08e4: Already exists 
0f077c79022d: Already exists 
86c62cf28c36: Pull complete 
6f3ba24a1140: Pull complete 
Digest: sha256:b655b1793c57a8f36382c1fbf8c2fe77b440a45515e9e927d1cb1b3da8b85a9c
Status: Downloaded newer image for lscr.io/linuxserver/tautulli:latest
7c7a2aebd39f3ab22c1b0c8a365f24b3d504d1d6bce1d42f610e9c41b2bb09d3
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Tautulli: https://tautulli.com/#donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...

The suggestion is to try ghcr.io/linuxserver/tautulli:latest, or indeed docker.io/linuxserver/tautulli:latest to see if you get the same issue, to rule out something interfering with the image layer download.

[scottdrmyers]

Ok thanks, this clears up the confusion. I didn't realize there were so many different images.

Tested the following:

ghcr.io/linuxserver/tautulli:latest = broken pipe
docker.io/linuxserver/tautulli:latest = broken pipe
ghcr.io/tautulli/tautulli:latest = working
lscr.io/linuxserver/tautulli:latest = broken pipe

I just wanted to bring this to someone attention as I have the same results on multiple different docker hosts, including a machine that I spun up in a VM quickly for testing.

I'm not going to worry about it, ghcr.io/tautulli/tautulli:latest is working and I'll just continue to use that. And yes, I was doing new deployments and specifying a different config path each time.

Something changed in the last update as everything was working fine, then the container updated and I can no longer deploy it from the three URLs above. Might as well close this if it's working for others here. Maybe something is affecting the image pull in between my host and the server, however, it just seems awfully weird it started happening for this container only... shrug

Thanks!

[thespad]

The image itself is definitely OK.

Can you try lscr.io/linuxserver/tautulli:develop and see if you get the same thing?

[scottdrmyers]

The image itself is definitely OK.

Can you try lscr.io/linuxserver/tautulli:develop and see if you get the same thing?

Yep same broken pipe issue.

2024-01-12T16:28:44.330033237Z s6-rc-init: fatal: unable to supervise service directories in /run/s6-rc/servicedirs: Broken pipe

Going to get a buddy of mine to try and deploy it on his docker host this weekend and see what his results are. I'm willing to bet it'll work for him but if I see the same issue I'll update the thread. Again, if it's working for other people it's something environmental on my end most likely.

Thanks again!

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity