8000 [FATAL tini (7)] exec ./start.sh failed: No such file or directory when starting docker image · Issue #1341 · slskd/slskd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[FATAL tini (7)] exec ./start.sh failed: No such file or directory when starting docker image #1341

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.

Sign up for GitHub

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

Jump to bottom
Open
tordenflesk opened this issue Apr 29, 2025 · 1 comment
Open

[FATAL tini (7)] exec ./start.sh failed: No such file or directory when starting docker image #1341

tordenflesk opened this issue Apr 29, 2025 · 1 comment

Comments

@tordenflesk
Copy link

[FATAL tini (7)] exec ./start.sh failed: No such file or directory

stack:

version: "3"
services:
slskd:
environment:
- SLSKD_REMOTE_CONFIGURATION=true
ports:
- 5030:5030/tcp
- 5031:5031/tcp
- 50300:50300/tcp
volumes:
- /Docker_Config/SLSKD:/app
- /srv/dev-disk-by-uuid-5c3c71b2-dce8-4967-95f4-eba3d293a511/slskd:/slskd
- /srv/dev-disk-by-label-DATA02/Music:/music:ro
image: slskd/slskd:latest
@jpdillingham
Copy link
Member

It looks like you're mounting a volume on the internal /slskd directory where the application sits, so the entrypoint must be looking in your volume instead of the container.

If you intended to map the settings and data, change that to /app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tordenflesk @jpdillingham
0