docker fails to start after reboot
Description
Problem/Justification
Impact
Activity
Bug Clerk December 16, 2024 at 5:44 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.
Chase Zeigler December 16, 2024 at 12:23 PM
I managed to fix it. Couldn't begin to tell you if it was the right way to do it or not, lol.
I ended up deleting /etc/docker/daemon.json which allowed me to get the docker service to start up. Then I deleted /mnt/.ix-apps/docker/network/files/local-kv.db. After unsetting and resetting the pool from the GUI, all my apps appeared, crashed, but they were there. Simply starting the containers got them running from that point.
Chase Zeigler December 16, 2024 at 4:07 AM
Debug log uploaded.
Bug Clerk December 16, 2024 at 3:43 AM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee
Reporter
Labels
Fix versions
Affects versions
Priority
UndefinedMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Rebooted my NAS and got "error in apps service"
checking the logs shows
Error initializing network controller: error creating default "bridge" network: cannot create network 8bb1b5602637abed921a8f390cbe1b22067349a7558b28ae3feac11a21fcb01b (docker0): conflicts with network 9f9afc36852427941ff7fb516fd4b7058581d7f05a4a0ac5cf745c92bb541488 (docker0): networks have same bridge name
Session ID: dafc2188-940a-1547-334e-fd33cfe2db2c