stoatchat/self-hosted
1
0
Fork 0
mirror of https://github.com/stoatchat/self-hosted.git synced 2026-07-21 04:25:24 -04:00
Code Issues 42 Packages Projects Releases Wiki Activity

bug: Docker Compose up "Context Canceled manifest unknown" #91

New Issue
Closed
opened 2026-02-16 12:51:25 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 12:51:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @Warrennoa on GitHub (Feb 10, 2025).

Originally assigned to: @DeclanChidlow on GitHub.

What happened?

I tried to setup this service for the first time
Debian 12
Completely fresh OS.

It looks like whenever I get to the docker compose part, I will get an error. I've tried pre-pulling, no matter what I get this error

#[+] Running 13/13
✘ january Error context canceled 0.9s
✘ events Error context canceled 0.9s
✘ api Error context canceled 0.9s
✘ rabbit Error context canceled 0.9s
✘ minio Error context canceled 0.9s
✘ crond Error context canceled 0.9s
✘ redis Error context canceled 0.9s
✘ createbuckets Error context canceled 0.9s
✘ autumn Error context canceled 0.9s
✘ web Error context canceled 0.9s
✘ pushd Error manifest unknown 0.9s
✘ caddy Error context canceled 0.9s
✘ database Error context canceled 0.9s
Error response from daemon: manifest unknown

I noticed the repository got updated 2 hours prior, so I don't know if that has anything to do with it.

Originally created by @Warrennoa on GitHub (Feb 10, 2025). Originally assigned to: @DeclanChidlow on GitHub. ### What happened? I tried to setup this service for the first time Debian 12 Completely fresh OS. It looks like whenever I get to the docker compose part, I will get an error. I've tried pre-pulling, no matter what I get this error #[+] Running 13/13 ✘ january Error context canceled 0.9s ✘ events Error context canceled 0.9s ✘ api Error context canceled 0.9s ✘ rabbit Error context canceled 0.9s ✘ minio Error context canceled 0.9s ✘ crond Error context canceled 0.9s ✘ redis Error context canceled 0.9s ✘ createbuckets Error context canceled 0.9s ✘ autumn Error context canceled 0.9s ✘ web Error context canceled 0.9s ✘ pushd Error manifest unknown 0.9s ✘ caddy Error context canceled 0.9s ✘ database Error context canceled 0.9s Error response from daemon: manifest unknown I noticed the repository got updated 2 hours prior, so I don't know if that has anything to do with it.
yindo added the bug label 2026-02-16 12:51:25 -05:00
yindo closed this issue 2026-02-16 12:51:25 -05:00
yindo commented 2026-02-16 12:51:25 -05:00
Author
Owner
Copy Link
Copy Source

@DeclanChidlow commented on GitHub (Feb 10, 2025):

Can reproduce. Investigating.

@DeclanChidlow commented on GitHub (Feb 10, 2025): Can reproduce. Investigating.
yindo commented 2026-02-16 12:51:25 -05:00
Author
Owner
Copy Link
Copy Source

@DeclanChidlow commented on GitHub (Feb 10, 2025):

Seems the incorrect tags were used. They were tagged 20250201-1 rather then 20250210-1 as they should have been.

@DeclanChidlow commented on GitHub (Feb 10, 2025): Seems the incorrect tags were used. They were tagged `20250201-1` rather then `20250210-1` as they should have been.
yindo commented 2026-02-16 12:51:25 -05:00
Author
Owner
Copy Link
Copy Source

@DeclanChidlow commented on GitHub (Feb 10, 2025):

@insertish The above change fixes the bulk of it, but your changes also specify a crond:20250210-1 though it is only available in a debug version (ghcr.io/revoltchat/crond:20250210-1-debug). It also looks like the cron container is missing uname stuff. I'll leave you to advise.

For anyone experiencing this issue, you'll need to replace all instances of 20250201-1 with 20250210-1 and the tag for crond with 20250210-1-debug for the time being.

@DeclanChidlow commented on GitHub (Feb 10, 2025): @insertish The above change fixes the bulk of it, but your changes also specify a `crond:20250210-1` though it is only available in a debug version (`ghcr.io/revoltchat/crond:20250210-1-debug`). It also looks like the cron container is missing uname stuff. I'll leave you to advise. For anyone experiencing this issue, you'll need to replace all instances of `20250201-1` with `20250210-1` and the tag for crond with `20250210-1-debug` for the time being.
yindo commented 2026-02-16 12:51:25 -05:00
Author
Owner
Copy Link
Copy Source

@insertish commented on GitHub (Feb 11, 2025):

Oops, fixed 400a603122
Not sure why crond didn't publish also, I'll look into it

@insertish commented on GitHub (Feb 11, 2025): Oops, fixed 400a60312266c4797e9a6fcda6b6e5cf941de9a0 Not sure why crond didn't publish also, I'll look into it
yindo commented 2026-02-16 12:51:25 -05:00
Author
Owner
Copy Link
Copy Source

@Warrennoa commented on GitHub (Feb 11, 2025):

Thank you all, I thought I was going crazy, my build is very very very basic so I was looking for typos for an hour or 2

@Warrennoa commented on GitHub (Feb 11, 2025): Thank you all, I thought I was going crazy, my build is very very very basic so I was looking for typos for an hour or 2
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
help wanted
improvement
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#91
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?