-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Docker startup broken in master for aboot due to systemd upgrade #7372
Comments
For reference, here is the
|
I bisected this to working with Build 640. Looking at the diff between the original 635 and 641 I suspected the systemd upgrade suggesting me to try the 640 image which seems to work. Output of the 640 working build:
|
I tested building my own master with a revert of 4369361 and that seems to work. |
do you have this one? systemd.unified_cgroup_hierarchy=0 in the /proc/cmdline after the system boots? this one is required. |
we missed aboot changes in this commit 63885ca |
@Staphylo , we need this in the aboot.j2 |
@lguohan, I'll make a PR right away |
Recent systemd upgrade from sonic-net#7228 requires an extra cmdline parameter for dockerd to start properly. Updating boot0 was missed as part of the systemd upgrade change. This change fixes sonic-net#7372 Signed-off-by: Samuel Angebault <[email protected]>
@bluecmd, you can temporarily work around this issue by running the following command on your switch. The content of the |
Why I did it Recent systemd upgrade from #7228 requires an extra cmdline parameter for dockerd to start properly. Updating boot0 was missed as part of the systemd upgrade change. How I did it Just added the missing cmdline parameter in files/Aboot/boot0.j2 This change fixes #7372 How to verify it Boot the image and dockerd should start normally.
Why I did it Recent systemd upgrade from #7228 requires an extra cmdline parameter for dockerd to start properly. Updating boot0 was missed as part of the systemd upgrade change. How I did it Just added the missing cmdline parameter in files/Aboot/boot0.j2 This change fixes #7372 How to verify it Boot the image and dockerd should start normally.
Why I did it Recent systemd upgrade from sonic-net#7228 requires an extra cmdline parameter for dockerd to start properly. Updating boot0 was missed as part of the systemd upgrade change. How I did it Just added the missing cmdline parameter in files/Aboot/boot0.j2 This change fixes sonic-net#7372 How to verify it Boot the image and dockerd should start normally.
Why I did it Recent systemd upgrade from sonic-net#7228 requires an extra cmdline parameter for dockerd to start properly. Updating boot0 was missed as part of the systemd upgrade change. How I did it Just added the missing cmdline parameter in files/Aboot/boot0.j2 This change fixes sonic-net#7372 How to verify it Boot the image and dockerd should start normally.
Description
Using current image I am trying to boot it on my Arista 7050 QX32. Image calls itself
image-master.641-782b02d9
.NOTE: This worked fine using the latest image from April 17 (
image-master.640-f8d38aee
).I receive the following on boot:
[FAILED] Failed to start Docker Application Container Engine.
Extra logs:
Steps to reproduce the issue:
Describe the results you received:
Docker fails to boot.
Describe the results you expected:
Image booted with default configuration.
Output of
show version
:N/A,
show
does not work without Docker.Output of
show techsupport
:N/A,
show
does not work without Docker.Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: