Closed boarder2 closed 1 year ago
Thanks for the report! This should now be fixed; looks like something changed in Alpine 3.18 so it wasn't creating a parent directory it was expecting to be there.
Thanks for the report! This should now be fixed; looks like something changed in Alpine 3.18 so it wasn't creating a parent directory it was expecting to be there.
Looks good now! Thanks for the quick turn around!
Describe the Bug
Since
smb-20230509
, when the container starts it floods the docker output with the followingRolling back to the
smb-20230508
image, it behaves as expected.Expected Behavior
No errors
Steps to Reproduce
Run with latest image
How You're Launching the Container
Container Logs
Additional Context
No response