Add daemon.json with overlay2 to fix container startup issue#351
Conversation
6b58436 to
5110a47
Compare
ee1ab22 to
34d3f78
Compare
4a3f4e2 to
686f4fa
Compare
a2838e3 to
f720386
Compare
f720386 to
e876a84
Compare
c4934ed to
46d9f21
Compare
|
Before switching |
9022047 to
5319537
Compare
We did try adding /var/lib/docker to PERSISTENT_BIND_PATHS before changing the data-root to /opt/docker-data. But because on EMT OS /var is often temporary (tmpfs) early in boot, Docker’s data under /var/lib/docker wasn’t actually persistent, so the overlayfs errors continued. Changing Docker’s data-root to /opt/docker-data and ensuring it is persistent and created at runtime fixed the problem. |
00d09b3 to
7b082d9
Compare
8601739
into
open-edge-platform:3.0-dev
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
1 similar comment
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
1 similar comment
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
1 similar comment
|
Automated Messages: Label 'moby-engine' has been added to this Pull Request. |
Merge Checklist
All boxes should be checked before merging the PR
Description
On EMT OS, when we tried to start Docker, it failed because the default overlay2 storage driver requires a writable, overlay-compatible filesystem, but /var/lib/docker resides under /var, which on EMT OS can be mounted as read-only or which isn’t compatible with overlay operations. This prevented Docker from launching. To fix this, we configured Docker to store its data in /opt/docker-data, a persistent and writable location that supports overlay2, by adding a daemon.json file and updating the RPM spec to create the required directories, install the configuration, and safely migrate any existing data from /var/lib/docker using rsync. With this change, Docker now starts and runs reliably on both RT and non-RT EMT OS, using a stable and compatible storage location.
Any Newly Introduced Dependencies
No
How Has This Been Tested?
Tested manually.