Skip to content

[BUG] 4.1.1-ls393 s6 startup error #572

@phelpsw

Description

@phelpsw

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Updating to this release resulted in nginx startup issue

$ docker logs swag
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle

Temporary Solution: Downgrading to 4.1.1-ls392 returns the service to a working state.

Running ps in the broken container:

@99c0bddb1a38:/root# busybox ps
PID   USER     TIME  COMMAND
    1 root      0:00 /package/admin/s6/command/s6-svscan -d4 -- /run/service
   17 root      0:00 s6-supervise s6-linux-init-shutdownd
   18 root      0:00 /package/admin/s6-linux-init/command/s6-linux-init-shutdownd -d3 -c /run/s6/basedir -g 3000 -C -B
   29 root      0:00 /bin/sh
  131 root      0:00 busybox ps
@99c0bddb1a38:/root# 

Attempting to restart the broken container

$ docker restart swag
swag

$ docker logs swag
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle

Expected Behavior

No response

Steps To Reproduce

Running a vanilla swag 4.1.1-ls393 should reproduce

Environment

- OS: ubuntu24.04

CPU architecture

x86-64

Docker creation

Will share snippet if determined relevant

Container logs

s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions