mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #321] 0.4.1 Container keeps restarting without log output #121
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#121
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 @santschi on GitHub (Oct 11, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/321
0.4.1 update broke my setup.
It's running on Debian Docker.
I cannot investigate more right now since I'm on the move but I'll check back in later this week.
@nitnelave commented on GitHub (Oct 11, 2022):
You should be able to safely revert to 0.4.0.
Feel free to check back in when you have more info.
@santschi commented on GitHub (Oct 11, 2022):
That's exactly what I did!
I love this minimal implementation btw! It's perfect for my uses!
Thank you so much!
@starkertyp commented on GitHub (Oct 12, 2022):
I'm not quite sure if this is related but I used
nitnelave/lldap:stableand ran into the following after the 0.4.1 upgrade:Rolling back to 0.4.0 works fine
@martadinata666 commented on GitHub (Oct 12, 2022):
Yes, the new image got different permission setup than prev image kindly look at README.md for updated compose
@santschi commented on GitHub (Oct 12, 2022):
Okay I got around to investigating as well. As @beji already discovered it was the permission changes that crashed the container continuously.
Maybe consider making permission changes a major version change in the future?
Thanks for the hint!
Thanks for all the effort you put in! It's truly an amazing project.
@nitnelave commented on GitHub (Oct 12, 2022):
Yeah, I apologize for that. The change was lost in a long list of changes to the docker image that were not related to the permissions, so I didn't realize its significance.