261

I finally figured out how to get docker up and running.

docker run --name my-forum-nodebb --link my-forum-redis:redis -p 80:80 -p 443:443 -p 4567:4567 -P -t -i nodebb/docker:ubuntu

I linked it to a redis instance, cool.

This is from scratch and I assume that when I created the redis instance

docker run --name my-forum-redis -d -p 6379:6379 nodebb/docker:ubuntu-redis

it pulls the image from a remote repo?

NodeBB offers a Dockerfile https://github.com/NodeBB/NodeBB/blob/master/Dockerfile I am not really quite sure how to use it. I am assuming that I can somehow create a local environment by calling this Dockerfile on my remote.

Is this correct? If so how can I create the local instance pointing to the remote?

BMW
  • 42,880
  • 12
  • 99
  • 116
Michael Joseph Aubry
  • 12,282
  • 16
  • 70
  • 135

8 Answers8

315

Download Dockerfile and Build a Docker Image

Download the Dockerfile to a directory on your machine, and from that same directory, run the following docker build command. Make sure to replace image_name with what you would like to name your image. Docker image naming restrictions can be found here.

docker build --tag 'image_name' .

This will give you an image on your local machine that you can create a container from. To do so, you'll need to run the following docker run command. Make sure to replace image_name with what you named your image in the previous command.

docker run --detach 'image_name'
Andria
  • 4,712
  • 2
  • 22
  • 38
Andreas Wederbrand
  • 38,065
  • 11
  • 68
  • 78
  • 1
    How does this work? If I just simply have the dockerfile how does it know about my project? Is there a link in the dockerfile? Then I assume if there is docker handles packaging a new image that I can then migrate over to my server. In this packaging it absorbs all the assets of my project? Sorry if I sound ignorant, docker is a new concept to me but I am enjoying learning. – Michael Joseph Aubry Mar 18 '16 at 06:48
  • 3
    Thanks by the way and what does the <> represent in your example why did you choose ? – Michael Joseph Aubry Mar 18 '16 at 06:48
  • No docker container knows about "your" project, they are very generic. – Andreas Wederbrand Mar 18 '16 at 12:36
  • 2
    This is answering a lot of my questions though https://docs.docker.com/engine/reference/builder/ – Michael Joseph Aubry Mar 18 '16 at 23:59
  • 2
    @MichaelJosephAubry dont enter the parameter verbatim. It's a placeholder to specify your own tag name eg 'docker build -t mytag .' – Ganesh Krishnan Nov 08 '19 at 16:31
118

While other answers were usable, this really helped me, so I am putting it also here.

From the documentation:

Instead of specifying a context, you can pass a single Dockerfile in the URL or pipe the file in via STDIN. To pipe a Dockerfile from STDIN:

$ docker build - < Dockerfile

With Powershell you can run:

Get-Content Dockerfile | docker build -

When the build is done, run command:

docker image ls

You will see something like this:

REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
<none>                     <none>              123456789        39 seconds ago      422MB

Copy your actual IMAGE ID and then run

docker run 123456789

Where the number at the end is the actual Image ID from previous step

If you do not want to remember the image id, you can tag your image by

docker tag 123456789 pavel/pavel-build

Which will tag your image as pavel/pavel-build

Nick Cox
  • 6,164
  • 2
  • 24
  • 30
Pavel Janicek
  • 14,128
  • 14
  • 53
  • 77
88

You cannot start a container from a Dockerfile.

The process goes like this:

Dockerfile =[docker build]=> Docker image =[docker run]=> Docker container

To start (or run) a container you need an image. To create an image you need to build the Dockerfile[1].

[1]: you can also docker import an image from a tarball or again docker load.

Auzias
  • 3,638
  • 14
  • 36
70

Straightforward and easy solution is:

docker build .
=> ....
=> Successfully built a3e628814c67
docker run -p 3000:3000 a3e628814c67

3000 - can be any port

a3e628814c68 - hash result given by success build command

NOTE: you should be within directory that contains Dockerfile.

zhisme
  • 2,368
  • 2
  • 19
  • 28
21

The title is what brought me here, this runs a container from a Dockerfile directly.

docker build --no-cache . |  grep "Successfully built" | sed 's/Successfully built //g' | xargs -I{} docker run {}
FreeSoftwareServers
  • 2,271
  • 1
  • 33
  • 57
8

With docker desktop 20.10.8

You can use a docker-compose file to name and configure your environment.

services:
    my_instance:
        build:
            context: .
            dockerfile: my_instance.dockerfile

Then docker compose up or docker compose run /bin/bash or whatever.

per https://docs.docker.com/compose/compose-file/compose-file-v3/#dockerfile

Stevko
  • 4,345
  • 6
  • 39
  • 66
5
docker run $(docker build -q .)
angordeyev
  • 511
  • 3
  • 11
4

enter image description here

We can see the docker file is inside the project folder E:\Code SAmple\flutqr

build command

docker build -t fluweb .
  • fluweb is the name for image you can specify any name
  • . represent current directory

Look at your docker desktop you can see your published images instead rickandmorty(i edited fluweb). enter image description here

if you want re run that image you can use That run button .else

enter image description here You can use this command

docker run rickandmorty

Now it live

enter image description here

lava
  • 6,020
  • 2
  • 31
  • 28
  • hi there ! <3 Flutter web. When you run this, we are creating the image correct? I'm confused on how to mount and run this image now – Gene Dec 09 '22 at 17:17