HELP/QUESTION Research failed start #1816
Replies: 10 comments 5 replies
-
|
BUMP |
Beta Was this translation helpful? Give feedback.
-
|
I'm also having this issue using docker compose. Though mine does not work properly when I start manually. |
Beta Was this translation helpful? Give feedback.
-
|
Changing to posgres 14 from latest fixed this for me |
Beta Was this translation helpful? Give feedback.
-
|
Confirm that. As @Dusky said, just downgrading postgres to 14 makes it work/autostart correctly. |
Beta Was this translation helpful? Give feedback.
-
|
It seems to me the next logical step here is to research if this is an upstream Postgres issue..? I’m not the person to research, even if I had the bandwidth right now 😔 Aside, it would be lovely not to have to babysit this for a minute every time Docker starts 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I had the same problem using docker compose. I was able to solve it just by changing the volume to an existing location: Default Change to something like Just make sure the folder structure is correct. |
Beta Was this translation helpful? Give feedback.
-
|
@renaldofreire please post your docker-compose.yml |
Beta Was this translation helpful? Give feedback.
-
I hope it helps See below: |
Beta Was this translation helpful? Give feedback.
-
|
This "miniflux-db" volume seems to never be used (it's empty here), but that's how miniflux started to work correctly. And I can't explain why. 😅 |
Beta Was this translation helpful? Give feedback.
-
|
@renaldofreire are you sure it's the volume PATH that made it work? In my case, after a lot of testing I found out that adding "restart" property to db container makes it finally work. Is there a reason why restart property is there for a miniflux container but NOT there for a db container? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
👋
Thanks for software
My Miniflux service won't start after I a) start macOS and/or b) Docker daemon but it will when I manually start it 😕 - anyone know why this may be?
Log
Before I manually start:
After I manually start:
I reinstalled macOS last week hoping this problem was an install quirk but it's not
Docker compose:
If you're experiencing this then please vote up (e.g. +1, like)
Welcome feedback/input
Hope this helps and to hear back
Cheers
Beta Was this translation helpful? Give feedback.
All reactions