Description
Problem/Justification
None
Impact
None
is blocked by
Katalon Manual Tests (BETA)
Activity
Show:
Automation for Jira December 19, 2022 at 3:08 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk December 17, 2022 at 1:50 PM
Bug Clerk December 16, 2022 at 5:14 PM
Bug Clerk December 15, 2022 at 11:02 PM
Waqar Ahmed July 3, 2022 at 5:34 PM
Seems like we are still blocked sadly 😞
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Time remaining
0m
Components
Fix versions
Priority
Low
Katalon PlatformLinked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created January 19, 2021 at 4:10 PM
Updated December 28, 2022 at 5:50 AM
Resolved December 28, 2022 at 5:41 AM
Kubernetes is deprecating and eventually going to remove use of docker directly. This does not mean that docker can't be used but just that dockershim won't be directly maintained by k8s upstream and instead we would have to configure some knobs to use docker.
Following with that, after initial investigation we have
An issue with containerd that it needs to be restarted once k3s has started and it definitely must already be running when k3s tries to start as otherwise it will fail. Why this happens is something related to k3s shipping containerd in it’s own codebase as well and i think we have a clash of sorts. Moving on, we don’t need to nuke k3s db as I tested creating deployments on docker and then when i used containerd, those deployments start and work fine. There are no issues apparently from the testing i have done so far. We however do lose existing pulled images and they need to be pulled again which k3s does automatically of course.
However let's please check this again especially with the newer version of k3s we have which has updated base packages and see if this is fixed, otherwise let's create an issue upstream. We should also see if using overlayfs would be an option with containerd as right now it uses the same snapshotter as docker ( docker uses containerd ) which results in huge number of datasets. Based on this we can make a decision on how we should move forward with either removing docker from our system and using containerd or keeping on using docker.