Bug 426457 - neondocker script is broken, because uses outdated api
Summary: neondocker script is broken, because uses outdated api
Status: REPORTED
Alias: None
Product: neon
Classification: KDE Neon
Component: Docker (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Jonathan Riddell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-12 22:02 UTC by Maksym Hazevych
Modified: 2020-12-20 19:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Traceback about outdated API (2.41 KB, text/plain)
2020-09-12 22:02 UTC, Maksym Hazevych 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maksym Hazevych 2020-09-12 22:02:40 UTC 
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
Comment 1 Ashley Stone 2020-12-20 19:06:53 UTC 
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