Docker: Difference between revisions

Browse history interactively

← Older edit Newer edit →

VisualWikitext

Revision as of 17:12, 19 December 2023 view source Admin (talk \| contribs) Image-reviewer, Bureaucrats, Check users, confirmed, Moderators (CommentStreams), Interface administrators, Push subscription managers, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), staff, Suppressors, sysadmin, Administrators, uploadaccess, upwizcampeditors, Widget editors 2,745 edits →Docker in Docker: more security focus ← Older edit		Revision as of 08:51, 14 January 2025 view source Admin (talk \| contribs) Image-reviewer, Bureaucrats, Check users, confirmed, Moderators (CommentStreams), Interface administrators, Push subscription managers, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), staff, Suppressors, sysadmin, Administrators, uploadaccess, upwizcampeditors, Widget editors 2,745 edits link to Docker Desktop (new article) Tag: Visual edit Newer edit →
Line 43:		Line 43:


	Note: '''Docker Desktop''' is simply a fancy GUI '''client''' application that uses virtualization (a Linux Virtual Machine) to bundle the Docker Engine into your host OS.		Note: '''[[Docker Desktop]]''' is simply a fancy GUI '''client''' application that uses virtualization (a Linux Virtual Machine) to bundle the Docker Engine into your host OS.

	*Volumes are the right choice when your application requires fully native file system behavior on Docker Desktop. For example, a database engine requires precise control over disk flushing to guarantee transaction durability. Volumes are stored in the Linux VM and can make these guarantees, whereas bind mounts are remoted to macOS or Windows OS, where the file systems behave slightly differently.		*Volumes are the right choice when your application requires fully native file system behavior on Docker Desktop. For example, a database engine requires precise control over disk flushing to guarantee transaction durability. Volumes are stored in the Linux VM and can make these guarantees, whereas bind mounts are remoted to macOS or Windows OS, where the file systems behave slightly differently.