Skip to main content

How to create a docker image and push it to Docker Hub

If you've been diving into the realm of docker containers, you've probably started dabbling with creating your own images and are looking to push those images to Docker Hub, so others can make use of your work. If that's the case, you're in luck; I'm going to walk you through that very process. Here we are going to create a new docker image and then push it to the Docker Hub — all from the command line.
This process isn't challenging, but you will want to know your way around the docker commands. I'll be demonstrating on a Ubuntu 16.04 Server, but the steps work on any Linux distribution that has docker installed. I will work under the assumption you already have docker installed and have an account on Docker Hub.
With that out of the way, let's get to work.

Creating your new image

For the sake of simplicity, we're going to create a new image, based on the latest Ubuntu image, which will include a LAMP server. Although there are tons of such images already available, this will serve as an easy example you can follow.
The first thing we must do is pull the latest Ubuntu image with the command:
docker pull ubuntu
The above command will pull down the latest Ubuntu image. Now we're going to create a container such that we can work within our latest Ubuntu. To do this, issue the command:
docker run --name test-lamp-server -it ubuntu:latest bash
You can use any name you like in the above command. I'm calling my test-lamp-server (so I know exactly what I'm working with). When the above command completes, you'll notice your terminal has changed to indicate you are now working within the container.
Once inside the container, the first thing you must do is update apt with the command:
apt-get update
If you do not issue the above command, you won't be able to install anything into the container. Once the update completes, issue the command:
apt-get install lamp-server^
The above command will install everything you need for your lamp server. During the installation process, you will be asked to create (and verify) a password for the MySQL "root" user (Figure A).
Figure A
Figure A
Creating your MySQL password within the container.
When the installation is complete, you need to exit the container with the exit command. Issue the command docker ps -a and you should see the new container listed.

Pushing the container to Docker Hub

Now it's time we push our new container to Docker Hub. Remember, this is just a test container, so chances of you actually wanting to push such a container to the hub will be slim. We'll do it anyway (so you know how it's done). The first thing you must do is commit the change with the command:
docker commit -m "Added LAMP Server" -a "NAME" test-lamp-server USER/test-lamp-server:latest
Where NAME is your full name and USER is your Docker Hub user name.
Next we need to login to Docker Hub with the command:
docker login
You will be prompted for your Docker login credentials. Upon successful authentication, you will see Login Succeeded. Finally, you can push your image to Docker Hub with the command:
docker push USER/test-lamp-server
Where USER is your Docker Hub user name. The image will be uploaded to Docker Hub and you're good to go. You can now pull that image back into docker from anywhere (so long as you have docker installed). Open up a web browser, log into Docker Hub, and you should see your image listed.

Develop your containers



At this point, you should be ready to start developing your containers and pushing them to the Docker Hub. Yes, we only created a very basic image here, but you can use all of your developer (and new-found docker) skills to create many varied images that will be useful to you, your colleagues, and the community at large.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,