10. Docker – Implementation => How to RUN and REMOVE a Container.

-

Docker – Implementation => How to RUN and REMOVE a Container.



RUN a Container.

01. Build an image   =>

 docker build -f Dockerfile_name -t give_a_name_to_image

 If docker file name is Dockerfile,

docker build . -t give_a_name_to_image

Otherwise

docker build -f abc -t docker_springboot_h2 .                                                                                                                                                                                                                                                                                                                   

02. Show images   =>     docker images

      Show images list  => docker image ls

03. VIEW ALL CONAINER PROCESS   => docker ps -a

04. RUN A CONTAINER   => 

docker run -p 8082:8080 --name containerName -d image_name_OR_id 

               -p 8082:8080 :- 8082:FOR LOCAL ACCESS THE CONTAINER. 8080 IS FOR INSIDE THE CONTAINER.

               WE HIT TO localhost:8082 AND THEN GO TO THAT CONTAINER AND 8082 is MAP WITH 8080.

 

05. CURRENTLY RUNNUNG CONTAINERS    => docker container ls

06. docker container log   => docker logs springboot_h2_container

07. Kill a container   => docker kill container_name_OR_id

08. docker start container_name_or_id

 

REMOVE a Container.

 

01. FIRST CONTANERS SHOULD BE REMOVED, THEN IMAGE SHOULD BE REMOVED

 

1. KILL A CONTAINER => Docker kill container_name_OR_id

                            OR

1. STPO A CONTAINER => docker stop controller_name_OR_id

2. REMOVE A CONTAINR => container rm container_name_OR_id

3. REMOVE AN IMAGE => docker rmi image__name_OR_id

4. RUN  docker container ls  AND docker images TO CHECK WHETHER SUCCESSFULLY REMOVE OR NOT

Comments

Post a Comment

Popular posts from this blog

09.Data Binding.

-
Image
Data Binding. Data binding ආකාර 2 කි. One-way Data Binding - component to view (DOM) or view to the component Two-way Data Binding - component to view and view to the component. One-way Data Binding in Angular Component to view (DOM) or view to component One-way data binding will bind the data from the component to the view (DOM) or from view to the component. One-way data binding is unidirectional. You can only bind the data from component to the view or from view to the component. a). From Component to View      01.   Interpolation Binding      02.   Property Binding      03.   Attribute Binding      04.   Class Binding      05.   Style Binding b). From View to Component      01.  Event binding  From Component to View     Style and Class Binding Directives – Directives are nothing but custom html element that angular provi...
Read more

Data Normalization

-
Image
  DATA NORMALIZATION This is a technique of splitting a complex table in to simple meaningful tables. In here arrange tables, rows and relationships between tables in order to avoid data redundancy ( අතිරික්තතාව ) and to attain data integrity ( සම්පූර්ණත්වය ).Goal, 01.    To avid data redundancy (data duplicated). 02.    To attain data integrity - Data goes to inconsistence state ( ස්ථිර නෑ , අදාළ නෑ ) . 03.    To put data in to correct table. 04.    To avoid CRUD anomalies ( අක්‍රමිකතාව ). Duplicate වෙන data නවත්වන්න ඕනේ , අදාළ නැති data store වීම නවත්වන්න   ඕනේ.නියමිත table වලට පමණක් නියමිට data යවන්න ඕනේ සහ DB එක සමග කරන CRUD operation වලදී අක්‍රමිකතා ඇති වෙන්න බෑ (අනවශ්‍ය data delete වීම , අනවශ්‍ය data add වීම ,data search කරගන්න බැරිවීම වගේ ඒවා) Partial dependency It is the dependency where non key attributes are functionally depends on any part of composite key. Full dependency It is the dependency where non ke...
Read more

Why you see it in IntelliJ but not in your project folder

-
Image
  Why you see it in IntelliJ but not in your project folder IntelliJ shows all dependencies under External Libraries, but they are not stored directly inside your project directory. Instead, they are downloaded and cached by your build tool (like Gradle or Maven) in a global location on your system. ~ /.gradle/ caches/modules- 2 /files- 2.1 / ~ / .m2 / repository/ You have a Maven project that uses a:1.2 → it downloads the JAR to ~/.m2/repository. Now, in a Gradle project, you also want to use a:1.2 What actually happens: Gradle does not use Maven’s .m2/repository directly. Instead: Gradle will check its own cache: ~/.gradle/caches/modules-2/files-2.1/ If a:1.2 is not found in Gradle's cache, it will: Download a:1.2 from the remote repository (e.g., Maven Central) again. Store it in the Gradle cache, not reuse from .m2. Why this happens: Gradle and Maven use different caching strategies and metadata formats, so they maintain separate repositories. BUT: You can configure Gradle to l...
Read more