Docker images stuck in odd state, can't start any

LiX47

Dabbler
Joined
Nov 4, 2021
Messages
24
I have three docker images on one of my installations. They're all currently in the stopped state (and should be), however two show 0 pods, 1 deployment, another shows 2 pods 1 deployment. I cannot start any of them, the ui shows them stuck at "deploying", here's a sample log from the "application events" of one:

Code:
2023-03-05 2:05:56
error killing pod: failed to "KillPodSandbox" for "354877e9-5705-4f0c-af83-03a51856f915" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"neos-ix-chart-7579ddbc85-kd84g_ix-neos\" network: plugin type=\"multus\" name=\"multus-cni-network\" failed (delete): DelegateDel: error invoking DelegateDel - \"macvlan\": error in getting result from DelNetwork: Link not found"
2023-03-05 2:05:45
error killing pod: failed to "KillPodSandbox" for "354877e9-5705-4f0c-af83-03a51856f915" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"neos-ix-chart-7579ddbc85-kd84g_ix-neos\" network: cni config uninitialized"
2023-03-05 2:01:19
error killing pod: failed to "KillPodSandbox" for "354877e9-5705-4f0c-af83-03a51856f915" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"neos-ix-chart-7579ddbc85-kd84g_ix-neos\" network: plugin type=\"multus\" name=\"multus-cni-network\" failed (delete): DelegateDel: error invoking DelegateDel - \"macvlan\": error in getting result from DelNetwork: Link not found"
2023-03-05 1:59:29
Scaled down replica set neos-ix-chart-7579ddbc85 to 0 from 1
2023-03-05 1:59:29
Deleted pod: neos-ix-chart-7579ddbc85-kd84g
2023-03-05 1:36:19
Pod sandbox changed, it will be killed and re-created.
2023-03-05 1:36:18
Add eth0 [xxx.xxx.xxx.xxx/16] from ix-net
2023-03-05 1:36:18
Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "e21087461742a14f73f9065c3fb7a838c12086ea0c1fde5af06b3e5c042d8fb6" network for pod "neos-ix-chart-7579ddbc85-kd84g": networkPlugin cni failed to set up pod "neos-ix-chart-7579ddbc85-kd84g_ix-neos" network: plugin type="multus" name="multus-cni-network" failed (add): [ix-neos/neos-ix-chart-7579ddbc85-kd84g/:ix-neos-0]: error adding container to network "ix-neos-0": Link not found, failed to clean up sandbox container "e21087461742a14f73f9065c3fb7a838c12086ea0c1fde5af06b3e5c042d8fb6" network for pod "neos-ix-chart-7579ddbc85-kd84g": networkPlugin cni failed to teardown pod "neos-ix-chart-7579ddbc85-kd84g_ix-neos" network: plugin type="multus" name="multus-cni-network" failed (delete): DelegateDel: error invoking DelegateDel - "macvlan": error in getting result from DelNetwork: Link not found]
2023-03-05 1:36:16
Created pod: neos-ix-chart-7579ddbc85-kd84g
2023-03-05 1:36:16
Successfully assigned ix-neos/neos-ix-chart-7579ddbc85-kd84g to ix-truenas
2023-03-05 1:36:08
MountVolume.SetUp failed for volume "kube-api-access-6fn6p" : object "ix-neos"/"kube-root-ca.crt" not registered
2023-03-05 1:36:07
MountVolume.SetUp failed for volume "kube-api-access-vgfpb" : object "ix-neos"/"kube-root-ca.crt" not registered
2023-03-05 1:36:05
MountVolume.SetUp failed for volume "kube-api-access-lcv28" : object "ix-neos"/"kube-root-ca.crt" not registered
2023-03-05 1:36:04
Predicate TaintToleration failed
2023-03-05 1:36:04
Predicate TaintToleration failed
2023-03-05 1:36:04
Predicate TaintToleration failed
 

LiX47

Dabbler
Joined
Nov 4, 2021
Messages
24
I figured it out, apparently during a system update the required field for network interface was either introduced and not auto-filled, or cleared out by something on all of my docker images. Figured it out because when trying to update an image, it was complaining about failing to use a network interface that didn't exist
 

Kelp07

Dabbler
Joined
Aug 14, 2022
Messages
12
Hi, thank you for posting this. I had the same problem and this helped me solve it.

I went to Apps, Settings, Advanced Settings. For "Route v4 Interface" I used the system's main interface and for Route v4 Gateway I used my router's IP address. Took a few minutes to update catalogs and then everything worked fine.
 
Top