DEV Community: Mahesh Jagtap

Upgrade Go version on Linux mint

Mahesh Jagtap — Tue, 26 Jul 2022 14:11:31 +0000

I was using Go version 1.13.8 which is latest if you install it using "apt-get install golang-go" command on linux mint or ubuntu.

Now I wanted to use generics and kafka-go package, which is not available for Go version less that 1.18 and 1.15 respectively.

So I decided to upgrade the Go version. But as I surf through the internet, I was not able to find a concrete solution for this.

So after much surfing and trial and error, here is the procedure I followed:
If you have installed the Go using above method, then:
first remove the older version using:

sudo apt-get remove golang-go

and

sudo apt-get remove --auto-remove golang-go

The above command must have uninstall the older version of Go from your system. Check it using go version

Now,If it is present, delete the go folder from usr/local.

After that, get the latest version file of Go for Linux(It was 1.18.4 at the time of writing this blog) using:

wget https://go.dev/dl/go1.18.4.linux-amd64.tar.gz

Manually untar it or use tar command as:

tar -xvf go1.18.4.linux-amd64.tar.gz

and move it to usr/local, manually using "Files" or using command:

mv go /usr/local

Now this has been taken care of, we have to define the GOROOT, GOPATH and PATH variables in profile file. For system wide permanent effect copy following three lines and paste them into /etc/profile file:

export GOROOT=/usr/local/go
export GOPATH=$HOME/<path to where your all go projects lies>
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH

OR, if you want the changes for that particular session, you can run above "export" commands in your terminal.

Now check go version, it should show you the one you installed.

Thanks for reading!

Solution for "error: connect econnrefused [container_ip]:3306"

Mahesh Jagtap — Thu, 23 Apr 2020 15:21:01 +0000

Hi guys,

There are many more reasons for this error. In some, users had used wrong port for MySQL in node application, in others 3306 port was already in use etc.

But for me, it was "docker-compose.yml" file issue. FYI, I am using 3 different containers for React, Node, and MySQL.

The issue was that, I was using "image" in docker-compose file for database service like this:

It was all right, untill I used volumes in dbservice. But after using volumes in dbservice it throws the above error.

The solution was to modify the docker-compose file like this:

and then adding following to Dockerfile:

//Dockerfile start
FROM mysql
//Dockerfile end

I hope you understood the solution. If have any queries, please feel free to ask it in a comment section.

Thank You.

Docker Basics - Part I

Mahesh Jagtap — Sun, 05 Apr 2020 12:28:36 +0000

Before starting, I assume that you know the following topics:
What is Docker? (Its a Containerization Technology.)
What is Containerization? (It is a virtualization method that uses single OS to power multiple distributed application.)
Why to use Docker? (So that we can manage dependencies and configuration needed for different application.)

If you understand above points, then you are ready to go with Docker commands; else, please check the following link: What is Docker?

For installation of docker please refer this article: Mac Windows Linux

Docker Commands

Now, let's run through the docker commands using question-answer paradigm for easy understanding.
1 What should be our first command?

A: We should Check if the docker service is up and running. For starting docker service in Linux, use:

$ service docker start

2 Now, the service has started, so can we create a container now?

A: Yes, indeed! For creating container, you will need an image. you can search the required image at dockerhub. In this tutorial, we are using "busybox" image. So, in search box type 'busybox'. The first result will be official image. Click on that image, you will see tags section there. For this we will be using '1.31' as a tag. So, the structure of our command would be like:

$ docker run [Image Name]:[Tag]

For our example, it would be:

$ docker run busybox:1.31

3 Is our container ready? If yes, how can we validate that?

A: Yes, our container is ready and we can validate that using following command:

$ docker ps -a

What it will do is, it will print all the container that we created till now. In your case it will be only one and that is created from busybox image. Now in output you will get dome info about your newly created container like container ID, Image used, is container up and running or not? etc.

4 So, whats next we created a container, but can we know more about our container like, what is IP and other stuff?

A: Yes, we can see that using following command. It will be of prime importance when we will be using environmental variables, networking and Volumes:

$ docker inspect [container ID]

What are you asking, where can we get this [container ID]? Yes, I here you, You can get it from the output of command from 3rd question. see, its the first field. Just copy and paste that ID in this command.

5 Enough about containers,how can I check if the image is locally present or not?

A: Yes, you can check that with following command:

$ docker images

6 OK, that's good. But what if I want to assign a port to the container or give name of my choice?

A: You can do that too. This can be done by passing the so called arguments to the "docker run" command. Let's have some light on that too. The first argument we want to know about is detach mode of container. With this you don't have to stay on that particular container and still your container will be up and running in background. The argument you pass to the 'docker run' command is "-d". Let's have an example:

$ docker run -d busybox:1.31

You can also assign a destination port to your container like this:

$ docker run -p [dest_port]:[source_port] [image]:[tag]

You can also give specific name to your container with --name argument, like:

$ docker run --name bbapp busybox:1.31 //now your container name is bbapp.

You can also start your container in an interactive mode with -it tag. Have a try:

$ docker run -it busybox:1.31

7 Last but not least, when there will be much more containers to handle, we will need to remove some containers. we can do that with following command:

dokcer rm [container1_id/name]....[containern_id/name]

Example:

$ docker rm bbapp

Conclusion: Okay, that's it for this article. In next article we will start with how to create our own images by using images from docker hub: With and without dockerfile. Thanks for a read.