<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Debug School: Nilasish Chakraborty</title>
    <description>The latest articles on Debug School by Nilasish Chakraborty (@nilschak253_498).</description>
    <link>https://www.debug.school/nilschak253_498</link>
    <image>
      <url>https://www.debug.school/images/4c7IYELTUra9XNmwshBx56X4OxJ_RZlQjP2wnqTjj0U/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzIwMS8xOWYx/MWQzZS0xMGIyLTQ4/ZjEtOGU5YS1mNzAx/ZGY0ZDRmODAucG5n</url>
      <title>Debug School: Nilasish Chakraborty</title>
      <link>https://www.debug.school/nilschak253_498</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/nilschak253_498"/>
    <language>en</language>
    <item>
      <title>Git commands day 5</title>
      <dc:creator>Nilasish Chakraborty</dc:creator>
      <pubDate>Fri, 18 Nov 2022 07:26:40 +0000</pubDate>
      <link>https://www.debug.school/nilschak253_498/git-commands-day-5-3m8i</link>
      <guid>https://www.debug.school/nilschak253_498/git-commands-day-5-3m8i</guid>
      <description>&lt;p&gt;git init: To init or create a local repository&lt;br&gt;
git clone: to clone the remote repository to local&lt;br&gt;
git pull: to pull the changes remote repository to local(working dir)&lt;br&gt;
git add: to move the file to the staging area.&lt;br&gt;
git commit: to commit the code to the local repository&lt;br&gt;
git push: to push the code to the remote repository&lt;br&gt;
git stash: to stash the local changes in a temporary folder&lt;br&gt;
git stash pop: to pop the stashed changes&lt;br&gt;
git merge: to merge the changes between two local repos&lt;br&gt;
git fetch: to merge the change between two remote branches&lt;br&gt;
git cherrypick: to merge the particular change from feature to master branch or any branch&lt;br&gt;
git rm: remove the change or unstage it from local repo&lt;br&gt;
git tag : to tag the latest commit in a local branch&lt;br&gt;
git tag -d : delete the tag&lt;br&gt;
git mv : to move the file or changes between two folders in local repo&lt;br&gt;
git diff : to check the difference between two commits, two commit id need to be passed as arguments&lt;br&gt;
git log: to check the history of commit for a specific branch&lt;br&gt;
git log --oneline: to check the history in oneline&lt;br&gt;
git revert: to revert the latest changes or commits from local branch&lt;br&gt;
git status: to check the status of the particular change or file&lt;br&gt;
git config user.name: we can configure the author name and etc. of the particular repo.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Day3 - How can we store container data in memory using docker volume</title>
      <dc:creator>Nilasish Chakraborty</dc:creator>
      <pubDate>Wed, 16 Nov 2022 05:32:28 +0000</pubDate>
      <link>https://www.debug.school/nilschak253_498/day3-how-can-we-store-container-data-in-memory-using-docker-volume-4enm</link>
      <guid>https://www.debug.school/nilschak253_498/day3-how-can-we-store-container-data-in-memory-using-docker-volume-4enm</guid>
      <description>&lt;p&gt;When we create a volume, it gets created in the local environment. When we run the container, the same file gets stored in the tmpfs and when the container is stopped, the tmpfs goes away and we can see the file in the local FS. So, In short, we can use the Docker's tmpfs feature to store container data in memory using docker volume. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Day2: Docker images</title>
      <dc:creator>Nilasish Chakraborty</dc:creator>
      <pubDate>Tue, 15 Nov 2022 06:40:59 +0000</pubDate>
      <link>https://www.debug.school/nilschak253_498/day2-docker-images-2ckh</link>
      <guid>https://www.debug.school/nilschak253_498/day2-docker-images-2ckh</guid>
      <description>&lt;p&gt;What is a Docker image. Explain in 10 points.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Docker image is a repository.&lt;/li&gt;
&lt;li&gt;100s of base docker images are stored in hub.docker.com called registry.&lt;/li&gt;
&lt;li&gt;Docker image consists of multiple filesystems -- ROOTFS + USERFS + ... //This both together are called base image&lt;/li&gt;
&lt;li&gt;File systems are called layers as they are on top of each other in the docker images.&lt;/li&gt;
&lt;li&gt;Each layer has a unique shad ID.&lt;/li&gt;
&lt;li&gt;Docker image consists of multiple filesystems OR it is a collection of multiple filesystems.&lt;/li&gt;
&lt;li&gt;Docker image has file system versioning.&lt;/li&gt;
&lt;li&gt;For encrypting docker images, sha2-256bit algorithm is used.&lt;/li&gt;
&lt;li&gt;All these layers merge to create one layer called mount.&lt;/li&gt;
&lt;li&gt;Mount gets attached during runtime to the user.&lt;/li&gt;
&lt;li&gt;If you change any file in a running container and stop it. The data will be stored at the diff directory. When the container will be restarted, then the file changes can be found intact. &lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Day-1 Docker Commands understand</title>
      <dc:creator>Nilasish Chakraborty</dc:creator>
      <pubDate>Mon, 14 Nov 2022 09:50:00 +0000</pubDate>
      <link>https://www.debug.school/nilschak253_498/day-1-docker-commands-understand-512h</link>
      <guid>https://www.debug.school/nilschak253_498/day-1-docker-commands-understand-512h</guid>
      <description>&lt;p&gt;what is the diff between docker pause and docker unpause&lt;br&gt;
Hint - docker stats&lt;/p&gt;

&lt;p&gt;----&amp;gt; Docker pause runs for only the running containers, not just the created ones whereas docker unpause only runs for paused containers not the stopped ones. If we run pause for a stopped container it's gonna give us a error message but not for a running container. Docker unpause will give the error message for a running or created container but not for a paused container.&lt;/p&gt;

&lt;p&gt;What is the diff between docker stop and docker kill&lt;br&gt;
Hints - Return value of linux + SIGNALs&lt;/p&gt;

&lt;p&gt;---&amp;gt; Docker stop usually stops the container and keeps a message "&lt;strong&gt;Exited (0) n seconds ago&lt;/strong&gt;" and Docker Kill gives the message "&lt;strong&gt;Exited (137) n seconds ago&lt;/strong&gt;". That means Docker stop doesn't deallocate the memory the container is using but docker kill deallocates the memory from the container.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Docker Understanding</title>
      <dc:creator>Nilasish Chakraborty</dc:creator>
      <pubDate>Mon, 14 Nov 2022 07:06:00 +0000</pubDate>
      <link>https://www.debug.school/nilschak253_498/docker-understanding-5392</link>
      <guid>https://www.debug.school/nilschak253_498/docker-understanding-5392</guid>
      <description>&lt;p&gt;What is Docker?&lt;br&gt;
--&amp;gt; It is a container management tool&lt;/p&gt;

&lt;p&gt;Why Docker?&lt;br&gt;
--&amp;gt; It gives us direct access to the System Kernel and create different environment for different applications.&lt;/p&gt;

&lt;p&gt;What is Container?&lt;br&gt;
--&amp;gt; Container is a running image which has it's own file system network and mount system.&lt;/p&gt;

&lt;p&gt;Docker workflow?&lt;/p&gt;

&lt;p&gt;Docker Resigtry(Hub) --&amp;gt; Docker Pull(image pull) + Docker Daemon talks to System Kernel + Docker Run (Creates container and runs the application)&lt;/p&gt;

&lt;p&gt;How container created?&lt;br&gt;
--&amp;gt; Docker Daemon talks to kernel and creates a isolated Linux/Windows Namespace system. Then it mounts the application code and Runs in an isolated environment by using the Host resources. &lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
