![]() Snaps runs on your local machine, while Docker containers run inside a lightweight virtual environment, isolated from one another, unless you explicitly expose network ports or mount directories/files from the host. Tl dr: You can accomplish the same things, but the intended use case is slightly different. To transfer to a new machine, you'd transfer the data, then use that with a new container. hold no state), so anything you want to keep (like database files) needs to be stored on the host. A container is supposed to be ephemeral (i.e. Similar to Snap, you don't really transfer Docker containers between instances. a web server, database server, application server, …). Docker is primarily targeted towards running services (e.g. It doesn't really do desktop apps, something which Snap can do. You can run multiple containers from the same image (at the same time). Similar to Snap, a Docker image contains everything needed to run a particular service. These machines (or containers) have their own IPs, you can set up networking between them etc. Do a new install and move the data as needed.ĭocker runs services inside containers (think of it as a lightweight VM). ![]() ![]() The app you install works like it normally would, so moving to a different machine works the same way. ![]() In a sense it is a replacement for distribution specific package management. He talked about some of the filesystem performance problems that can arise when using a shared volume from the host machine on Mac OS X, along with some potential workarounds and word of. They include everything that is needed to run the software, so you don't have to install additional dependencies manually. A couple of years ago, Will Pleasant-Ryan wrote Docker for Mac: Overcoming Slow Mounted Volumes, describing his desire to use Docker for local development. Snap installs apps on your local machine as self-contained packages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |