Docker - Revision history

Brodriguez: Add command

2023-07-19T22:42:16Z

Add command

← Older revision		Revision as of 22:42, 19 July 2023
Line 149:		Line 149:
	docker volume create <volume_name>		docker volume create <volume_name>
	Where {{ ic \|volume_name}} is the name the volume should use.		Where {{ ic \|volume_name}} is the name the volume should use.


			Examine logs of running docker instance:
			sudo docker logs -f <container_name>

Brodriguez: Add command

2023-07-19T22:33:40Z

Add command

← Older revision		Revision as of 22:33, 19 July 2023
Line 115:		Line 115:
	==== General Commands ====		==== General Commands ====

	List all docker containers:		List all live docker containers:
	docker ps		docker ps


			List all (including stopped) docker containers:
			docker ps --al

Brodriguez: Save commands

2023-07-06T04:48:31Z

Save commands

← Older revision		Revision as of 04:48, 6 July 2023
Line 6:		Line 6:

	[https://www.docker.com/ Docker] creates and runs '''containers''', which are sand-boxed processes, isolated from all other processes, with their own allocated cpu/memory/etc.		[https://www.docker.com/ Docker] creates and runs '''containers''', which are sand-boxed processes, isolated from all other processes, with their own allocated cpu/memory/etc.

			Each docker container is "meant to do exactly one thing, and do it well". So it's common to have a docker stack comprised of multiple containers. For example, one container to run your main application, and another for your database.


Line 37:		Line 39:

	Launch a built image as a new container instance:		Launch a built image as a new container instance:
	docker run -dp <~~ports_to_map~~> <~~optional_mount_command~~> <~~image_name~~>		docker run -d <image_name>
			Where {{ ic \|image_name}} - Corresponds to the name of the image you wish to create a container of.
			* See below sections for additional useful optional args.


			Example:
			docker run -d my-cool-image

			{{ warn \|With the above command, data will NEVER persist long term. If the container is ever restarted or rebuilt, all data in the container will be lost. See Mounting Subsection for solutions.}}


			===== Port Mapping Subsection =====

			To expose ports of a container instance to the host, we use port mapping.


			Command follows the format of:
			-p <host>:<host_port>:<container_port>
	Where:		Where:
	* {{ ic \|~~ports_to_map~~}} ~~corresponds~~ to the ~~{{ ic \|HOST:PORT:PORT}} values~~ to ~~map the container ports~~ to ~~the host~~.		* {{ ic \|host}} - Corresponds to the host address to connect to. Often {{ ic \|127.0.0.1}}.
	** Ex: A value of {{ ic \|127.0.0.1~~:3000:3000~~ }} ~~would map port 3000 on localhost to port 3000 on the container~~.		* {{ ic \|host_port}} - Corresponds to the port to use on the host machine for mapping.
	* {{ ic \|~~optional_mount_command~~}} - ~~Optional. See below~~ for ~~mount command explanations~~.		* {{ ic \|container_port}} - Corresponds to the port to connect to on the container.
	* {{ ic \|~~image_name~~}} - Corresponds to the ~~name of~~ the ~~image you wish to create a~~ container of.


	Example:		Example:
	docker run -dp 127.0.0.1:3000:3000 my-cool-image		docker run -d -p 127.0.0.1:3000:3000 my-cool-image

	~~{{ warn \|With the above command, data will NEVER persist long term. If the container is ever restarted or rebuilt, all data in the container will be lost.}}~~


Line 65:		Line 81:

	Example:		Example:
	docker run -~~dp 127.0.0.1:3000:3000~~ --mount type=volume,src=my-volume,target=/etc/my_volume my-cool-image		docker run -d --mount type=volume,src=my-volume,target=/etc/my_volume my-cool-image


Line 77:		Line 93:

	Example:		Example:
	docker run -~~dp 127.0.0.1:3000:3000~~ --mount type=bind,src=/srv/my_project/share_folder,target=/etc/my_volume my-cool-image		docker run -d --mount type=bind,src=/srv/my_project/share_folder,target=/etc/my_volume my-cool-image


			===== Command Network Subsection =====

			Docker '''networks''' are used to allow containers to connect and communicate among each other.


			Attach Network:
			--network <network_name>
			Where {{ ic \|network_name}} - Is the docker virtual network to connect in.


			Example:
			docker run -d --network my_network my-cool-image

Brodriguez: Add various commands and such

2023-07-06T03:32:45Z

Add various commands and such

@@ Line 5: / Line 5: @@
 == Docker ==
-The {{ ic |docker-compose.yml}} file defines the docker service to run.
+[https://www.docker.com/ Docker] creates and runs '''containers''', which are sand-boxed processes, isolated from all other processes, with their own allocated cpu/memory/etc.
 These two files should be put into the same directory. Then {{ ic |cd}} into the directory and build it with {{ ic |docker-compose run}}.
 Finally, start the service with {{ ic |docker-compose up -build -d}}.
 == Kubernetes ==
-Kubernetes is a an architecture that runs and manages docker-like containers for applications.
+[https://kubernetes.io/ Kubernetes] is a an architecture that runs and manages docker-like containers for applications.
 {{ note | This is a simplified overview of useful commands for using Kubernetes. For full official docs, see https://kubernetes.io/docs/concepts/overview/}}

Brodriguez: Update page formatting

2023-07-06T01:17:12Z

Update page formatting

← Older revision		Revision as of 01:17, 6 July 2023
Line 18:		Line 18:
	Kubernetes is a an architecture that runs and manages docker-like containers for applications.		Kubernetes is a an architecture that runs and manages docker-like containers for applications.

			{{ note \| This is a simplified overview of useful commands for using Kubernetes. For full official docs, see https://kubernetes.io/docs/concepts/overview/}}


			=== Kubernetes Sub Parts ===

	~~Consists of:~~
	* '''Control Plane''' - Where decisions are made.		* '''Control Plane''' - Where decisions are made.
	** Generally has 3 of these running, to ensure availability.		** Generally has 3 of these running, to ensure availability.
Line 36:		Line 39:
	*** '''Controller Manager''' - Manages the controllers.		*** '''Controller Manager''' - Manages the controllers.
	*** '''Key-Value Store''' - Effectively a "database of possible states".		*** '''Key-Value Store''' - Effectively a "database of possible states".

			=== Kubernetes Commands ===

			{{ todo \| Figure out common/useful commands and add here. }}

Brodriguez: Add initial kubernetes section

2023-07-06T00:55:55Z

Add initial kubernetes section

@@ Line 1: / Line 1: @@
-{{ todo | Page is very incomplete. Notes of learning docker here. }}
+{{ todo | Page is very incomplete. Notes of learning docker/kubernetes here. }}
 The {{ ic |docker-compose.yml}} file defines the docker service to run.
@@ Line 10: / Line 12: @@
 Finally, start the service with {{ ic |docker-compose up -build -d}}.

Brodriguez: Create page

2023-07-05T20:00:13Z

Create page

New page

{{ todo | Page is very incomplete. Notes of learning docker here. }}

The {{ ic |docker-compose.yml}} file defines the docker service to run.

The {{ ic |Dockerfile}} file defines the actual commands the docker instance should execute once it is created, in order to get our service.

These two files should be put into the same directory. Then {{ ic |cd}} into the directory and build it with {{ ic |docker-compose run}}.

Finally, start the service with {{ ic |docker-compose up -build -d}}.