Skip to content

fix restart issue #235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khaledk2 wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix restart issue #235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c7c10ed
fix restart issue
khaledk2 Sep 7, 2026
fa13851
improve the text
khaledk2 Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions Docker_Config_UoD_ESS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,3 +55,19 @@ Instructions
* Start the docker service

systemctl start docker


Restart Issue:
-------------

The restart issue on the VM: the machine restarts, but the containers do not restart with it.

This has been investigated on the merge-ci host (**ome-devsp-ap1**), it occurred because the Docker image disk (**docker-storage_ap1.img**) was not properly mounted to **/var/lib/docker-xfs-ap1**. To resolve this, The **/etc/fstab** file has been updated so the mount depends on the scratch folder being available and retries every 30 seconds if it fails, i.e.:

/uod/idr/scratch/docker-storage_ap1.img /var/lib/docker-xfs-ap1 xfs loop,defaults,x-systemd.requires-mounts-for=/uod/idr/scratch,,x-systemd.mount-timeout=30 0 0

The Docker service file has been updated so it relies on the mounted image disk. Specifically, the following clause has been appended to the end of both the **After** and **Requires** lines within the [Unit] section:

var-lib-docker\x2dxfs\x2dap1.mount

Following these adjustments, a system reboot successfully brought back all Docker containers. The identical fix has now been deployed to the active merge-ci host (**idr3-slot2**).