Skip to content

Update 'usingdocker' tutorial to name the container#1165

Merged
mdlinville merged 1 commit intodocker:masterfrom
mdlinville:tutorial_explain_naming
Jan 18, 2017
Merged

Update 'usingdocker' tutorial to name the container#1165
mdlinville merged 1 commit intodocker:masterfrom
mdlinville:tutorial_explain_naming

Conversation

@mdlinville
Copy link

Proposed changes

Update 'usingdocker' tutorial to name the container and do some basic clean-up on the topic's mark-up

Related issues (optional)

Fixes #990
Replaces #1163

Do some clean-up while I'm in there

* The `-d` flag runs the container in the background (as a so-called daemon).
* The `--name my_webapp` flag names the container `my_webapp`. If you do not
specify a name, Docker creates a random (and sometimes amusing) name for the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on sometimes amusing, thank you :D


In this case Docker has exposed port 5000 (the default Python Flask
port) on port 49155.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I felt this was kinda useful actually. What's your thinking in removing it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left it in, just moved it up a bit.

Copy link
Contributor

@sanscontext sanscontext left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with one question. Thank you for tackling this!

@mdlinville mdlinville merged commit 20fab8c into docker:master Jan 18, 2017
@mdlinville mdlinville deleted the tutorial_explain_naming branch January 18, 2017 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants