Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 task done
derMeister21 opened this issue Dec 30, 2024 · 7 comments

Comments

@derMeister21
Copy link

derMeister21 commented Dec 30, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I try do install Unifi Controller with docker compose on my Raspberry PI 4 with Openmediavault. MongoDB is Version 3.6 and is runnig. Testet with docker logs command. When I try docker logs command with unifi-network-application I'm getting this Error: "s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle"

unifi-network-application version 8.6.9-ls73 (latest)

Expected Behavior

No response

Steps To Reproduce

Config from your Github Site. Copy Paste

Environment

- OS: Debian 12 Bookworm / Newest Openmediavault (7)
- How docker service was installed: Docker in Openmediavault

CPU architecture

arm64

Docker creation

Openmediavault compose

Container logs

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

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

@thespad
Copy link
Member

thespad commented Dec 30, 2024

Please provide the output of docker info

@derMeister21
Copy link
Author

`pi@raspberrypi:~ $ sudo docker info
Client: Docker Engine - Community
Version: 27.4.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.19.3
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.1
Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 3
Running: 3
Paused: 0
Stopped: 0
Images: 6
Server Version: 27.4.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: **********
runc version: v1.2.2-0-g7cb3632
init version: ********
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.6.62+rpt-rpi-v8
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.703GiB
Name: raspberrypi
ID: ******
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

WARNING: No memory limit support
WARNING: No swap limit support`

I changed the IDs and made some *. If you need this i can give you also the IDs.

@thespad
Copy link
Member

thespad commented Dec 30, 2024

Can you run

docker exec <container name> ls -la /etc/s6-overlay/s6-rc.d/ci-service-check/

And

docker exec <container name> cat /etc/s6-overlay/s6-rc.d/ci-service-check/type

For the affected container

@derMeister21
Copy link
Author

derMeister21 commented Dec 30, 2024

`pi@raspberrypi:~ $ sudo docker exec unifi-network-application ls -la /etc/s6-overlay/s6-rc.d/ci-service-check/
total 12
drwxr-xr-x 3 0 0 4096 Dec 17 23:33 .
drwxr-xr-x 1 0 0 4096 Dec 24 17:39 ..
drwxr-xr-x 2 0 0 4096 Dec 17 23:33 dependencies.d
-rw-r--r-- 1 0 0 0 Dec 17 23:33 type
-rw-r--r-- 1 0 0 0 Dec 17 23:33 up
pi@raspberrypi:~ $ sudo docker exec unifi-network-application cat /etc/s6-overlay/s6-rc.d/ci-service-check/type'

Still the same error. Also after restarting the container.

@thespad
Copy link
Member

thespad commented Dec 30, 2024

Have you tried deleting and repulling the image? As you can see below the image you're using does not have zero-length files in that path:

image

@derMeister21
Copy link
Author

thank you very much that was the problem. After pulling the image it worked.

@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants