mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1808] [Bug]: Does not work after docker compose restart #1002
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1002
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @alexkutsan on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/koel/koel/issues/1808
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
docker-compose -f docker-compose.mysql.yml up -ddocker-compose -f docker-compose.mysql.yml exec koel php artisan koel:init --no-assetsdocker-compose -f docker-compose.mysql.yml downdocker-compose -f docker-compose.mysql.yml up -dExpected behavior
koel accesible after restart
Actual behavior
Error occurred when trying to access
Logs
Logs:
Koel version
v7.0.8
How did you install Koel?
Official Docker image
Additional information
MySql docker setup from https://github.com/koel/docker
@phanan commented on GitHub (Jul 29, 2024):
You’re not including the requested log.
On Mon, Jul 29, 2024 at 14:59 Alexander Kutsan @.***>
wrote:
@alexkutsan commented on GitHub (Jul 29, 2024):
Yep, my bad. Was trying to reproduce again. but failed earlier:
Logs :
@alexkutsan commented on GitHub (Jul 29, 2024):
Error above happenss because I bumped to koel 7.0.9.
Rolled back to 7.0.8 and reproduced issue.
Logs :
@alexkutsan commented on GitHub (Jul 29, 2024):
Same for
docker-compose.postgres.ymlHere is my:
@alexkutsan commented on GitHub (Jul 29, 2024):
From this discussion https://github.com/koel/koel/issues/1429
Found a workaround, that after running
After restart everything starts to work.
But I can't run this command manyally very time compose restarts.
May be
koel:initshould run automatically in docker after DB available?@phanan commented on GitHub (Jul 29, 2024):
I guess my question would be, why do you have to reset your Docker
environment everytime?
On Mon, Jul 29, 2024 at 15:51 Alexander Kutsan @.***>
wrote:
@alexkutsan commented on GitHub (Jul 29, 2024):
The machine that is running the container sometimes stops because it is not a cloud machine - it is Synology NAS at home, sometimes, there is no electricity. After it boots again - all container should automatically start (because of
restart:alwaysoption) and work well.@CCO19 commented on GitHub (Jul 30, 2024):
Hi,
Similar behavior on a new installation.
I initially had a Koel 7.0.8 container that worked. As the container update to 7.0.9 failed and my audio library is not yet colossal, I redid a new installation by deleting the initial volumes. However, my log is not quite the same :
@phanan commented on GitHub (Jul 30, 2024):
Just generate a new app key.
On Tue, Jul 30, 2024 at 03:11 CCO @.***> wrote:
@CCO19 commented on GitHub (Jul 30, 2024):
Hi @phanan, thanks for your reply.
I must be doing it wrong, I'm getting the same result but with different error logs:
@phanan commented on GitHub (Jul 30, 2024):
Ok I get it now. Unfortunately I’m on vacation and won’t be able to fix it
until later this week. Can you reverse to the previous version in the
meantime?
On Tue, Jul 30, 2024 at 11:49 CCO @.***> wrote:
@phanan commented on GitHub (Jul 30, 2024):
Or, you can try to manually install cron in your docker image by running
apt install cron -y
On Tue, Jul 30, 2024 at 12:04 An Phan @.***> wrote:
@CCO19 commented on GitHub (Jul 30, 2024):
No problem. I'll restore my backup of version 6.12.1 in the meantime.
Thanks for your work, Koel is great!
@phanan commented on GitHub (Jul 30, 2024):
I mean the previous 7.0.8 version should work just fine :)
On Tue, Jul 30, 2024 at 12:24 CCO @.***> wrote:
@phanan commented on GitHub (Jul 30, 2024):
And once this built
https://github.com/koel/docker/actions/runs/10160403469/job/28096789646
is complete, the docker should work too. Otherwise, yeah this will have to
wait until I’m back from vacation :)
On Tue, Jul 30, 2024 at 12:26 An Phan @.***> wrote:
@CCO19 commented on GitHub (Jul 30, 2024):
I also had 7.0.8 yesterday but I didn't back up yesterday before attempting the 7.0.9 update and since I deleted my volumes it's easier to restore my VM with the 6.12.1 container 😅
I quickly tried to install cron in the container but I didn't succeed because sudo is not recognized:
But don't worry, there's no hurry, enjoy your vacation! 😎🧳📷🌴
@alexkutsan commented on GitHub (Aug 1, 2024):
@phanan is there a planned solution to fix application startup after restarting the container? Generally, this is the main obstacle to this koel for my personal needs.
@phanan commented on GitHub (Aug 1, 2024):
TBH I don't have time to reproduce your issue yet (on vacation). But I don't really get why .env should be destroyed, as it's mounted as a volume. You can also add
APP_KEYinto the docker file to make sure it's persisted.@alexkutsan commented on GitHub (Aug 1, 2024):
Could you give some details about .env.
I don't see it mounted in compose file https://github.com/koel/docker/blob/master/docker-compose.postgres.yml
UPD:
Found info in https://github.com/koel/docker/tree/master?tab=readme-ov-file#how-to-bind-mount-the-env-file
After mounting in docker-compose .env file seems like everything works fine: