Skip to content

Updating Docker (FMA) causes Docker to become unusable #32227

@jmwatts

Description

@jmwatts

Fleet version: 4.72

Web browser and operating system:


💥  Actual behavior

Installing software...
Success
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>system-entities</key>
	<array>
		<dict>
			<key>content-hint</key>
			<string>Apple_HFS</string>
			<key>dev-entry</key>
			<string>/dev/disk5s2</string>
			<key>mount-point</key>
			<string>/private/tmp/dmg_mount_vXuyKW</string>
			<key>potentially-mountable</key>
			<true/>
			<key>unmapped-content-hint</key>
			<string>48465300-0000-11AA-AA11-00306543ECAC</string>
			<key>volume-kind</key>
			<string>hfs</string>
		</dict>
		<dict>
			<key>content-hint</key>
			<string>EFI</string>
			<key>dev-entry</key>
			<string>/dev/disk5s1</string>
			<key>potentially-mountable</key>
			<true/>
			<key>unmapped-content-hint</key>
			<string>C12A7328-F81F-11D2-BA4B-00A0C93EC93B</string>
			<key>volume-kind</key>
			<string>msdos</string>
		</dict>
		<dict>
			<key>content-hint</key>
			<string>GUID_partition_scheme</string>
			<key>dev-entry</key>
			<string>/dev/disk5</string>
			<key>potentially-mountable</key>
			<false/>
			<key>unmapped-content-hint</key>
			<string>GUID_partition_scheme</string>
		</dict>
	</array>
</dict>
</plist>
"disk5" ejected.
true
Quitting application 'com.docker.docker'...
Application 'com.docker.docker' quit successfully.
Image

🛠️ To fix

  • adjust the install script to quit relevant processes before install to ensure a successful upgrade

Product designer: @marko-lisica

🧑‍💻  Steps to reproduce

  1. Have an older version of Docker installed, configured, and functioning with containers on an enrolled host. Also have it running
  2. Add Docker FMA to Fleet Library, and attempt to upgrade either though Self service or Fleet Host Software page
  3. Wait for upgrade to complete. Note, docker does not quit even though Fleet thinks it did.
  4. Try to quit Docker. Ultimately have to force quit Docker.
  5. Attempt to launch Docker

🕯️ More info (optional)

Reinstalling via Fleet did not resolve the issue. Uninstalling and then reinstalling via Fleet resulted in a functioning Docker install, but all preferences and settings were lost.

Metadata

Metadata

Assignees

Labels

#g-softwareSoftware product group:help-solutions-consultingTasks for Solutions ConsultantsbugSomething isn't working as documentedfmarelates to a Fleet-maintained app~released bugThis bug was found in a stable release.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions