| Summary: | neondocker script is broken, because uses outdated api | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Maksym Hazevych <dpadar> |
| Component: | Docker | Assignee: | Jonathan Riddell <jr> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | major | CC: | ash |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Traceback about outdated API | ||
I have been able to reproduce this on fresh Neon installs. Apparently this cannot be reproduced on some older installations. Uploaded a rapid way of generating a environment that reproduces the issue, see: https://invent.kde.org/ash/bug-426457 Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding! |
Created attachment 131585 [details] Traceback about outdated API SUMMARY Started neondocker on stable Neon User Edition: 1. Got an message "Could not connect to Docker, check it is installed, running and your user is in the right group for access". Manually checked if my set-up is correct - it is. Then removed invocation of validate_docker function and proceeded. 2. After that got traceback with statement about starting container with non-empty request body was being removed since API v1.24. Searched the web - current API is 1.40 I wont try to edit script further, because have no knowledge in ruby. OBSERVED RESULT Fail on fail EXPECTED RESULT Working script