Gotchas in Writing Dockerfile. Hirokuni, K. 2014. abstract bibtex [Excerpt: Why do we need to use Dockerfile?] Dockerfile is not yet-another shell. Dockerfile has its special mission: automation of Docker image creation. [\n] Once, you write build instructions into Dockerfile, you can build the same image just with docker build command. [\n] Dockerfile is also useful to tell the knowledge of what a job the container does to somebody else. Your teammates can tell what the container is supposed to do just by reading Dockerfile. They don't need to know login to the container and figure out what the container is doing by using ps command. [\n] For these reasons, you must use Dockerfile when you build images. However, writing Dockerfile is sometimes painful. In this post, I will write a few tips and gochas in writing Dockerfile so that you love the tool. [\n] [...]
@article{hirokuniGotchasWritingDockerfile2014,
title = {Gotchas in Writing {{Dockerfile}}},
author = {Hirokuni, Kim},
year = {2014},
abstract = {[Excerpt: Why do we need to use Dockerfile?]
Dockerfile is not yet-another shell. Dockerfile has its special mission: automation of Docker image creation.
[\textbackslash n] Once, you write build instructions into Dockerfile, you can build the same image just with docker build command.
[\textbackslash n] Dockerfile is also useful to tell the knowledge of what a job the container does to somebody else. Your teammates can tell what the container is supposed to do just by reading Dockerfile. They don't need to know login to the container and figure out what the container is doing by using ps command.
[\textbackslash n] For these reasons, you must use Dockerfile when you build images. However, writing Dockerfile is sometimes painful. In this post, I will write a few tips and gochas in writing Dockerfile so that you love the tool.
[\textbackslash n] [...]},
keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-14042970,computational-science,docker,reproducible-research,research-management},
lccn = {INRMM-MiD:c-14042970}
}
Downloads: 0
{"_id":"ASmhCvSwNpFGJc4QJ","bibbaseid":"hirokuni-gotchasinwritingdockerfile-2014","downloads":0,"creationDate":"2016-06-22T10:19:28.215Z","title":"Gotchas in Writing Dockerfile","author_short":["Hirokuni, K."],"year":2014,"bibtype":"article","biburl":"https://sharefast.me/php/download.php?id=zOUKvA&token=29","bibdata":{"bibtype":"article","type":"article","title":"Gotchas in Writing Dockerfile","author":[{"propositions":[],"lastnames":["Hirokuni"],"firstnames":["Kim"],"suffixes":[]}],"year":"2014","abstract":"[Excerpt: Why do we need to use Dockerfile?] Dockerfile is not yet-another shell. Dockerfile has its special mission: automation of Docker image creation. [\\n] Once, you write build instructions into Dockerfile, you can build the same image just with docker build command. [\\n] Dockerfile is also useful to tell the knowledge of what a job the container does to somebody else. Your teammates can tell what the container is supposed to do just by reading Dockerfile. They don't need to know login to the container and figure out what the container is doing by using ps command. [\\n] For these reasons, you must use Dockerfile when you build images. However, writing Dockerfile is sometimes painful. In this post, I will write a few tips and gochas in writing Dockerfile so that you love the tool. [\\n] [...]","keywords":"*imported-from-citeulike-INRMM,~INRMM-MiD:c-14042970,computational-science,docker,reproducible-research,research-management","lccn":"INRMM-MiD:c-14042970","bibtex":"@article{hirokuniGotchasWritingDockerfile2014,\n title = {Gotchas in Writing {{Dockerfile}}},\n author = {Hirokuni, Kim},\n year = {2014},\n abstract = {[Excerpt: Why do we need to use Dockerfile?]\n\nDockerfile is not yet-another shell. Dockerfile has its special mission: automation of Docker image creation.\n\n[\\textbackslash n] Once, you write build instructions into Dockerfile, you can build the same image just with docker build command.\n\n[\\textbackslash n] Dockerfile is also useful to tell the knowledge of what a job the container does to somebody else. Your teammates can tell what the container is supposed to do just by reading Dockerfile. They don't need to know login to the container and figure out what the container is doing by using ps command.\n\n[\\textbackslash n] For these reasons, you must use Dockerfile when you build images. However, writing Dockerfile is sometimes painful. In this post, I will write a few tips and gochas in writing Dockerfile so that you love the tool.\n\n[\\textbackslash n] [...]},\n keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-14042970,computational-science,docker,reproducible-research,research-management},\n lccn = {INRMM-MiD:c-14042970}\n}\n\n","author_short":["Hirokuni, K."],"key":"hirokuniGotchasWritingDockerfile2014","id":"hirokuniGotchasWritingDockerfile2014","bibbaseid":"hirokuni-gotchasinwritingdockerfile-2014","role":"author","urls":{},"keyword":["*imported-from-citeulike-INRMM","~INRMM-MiD:c-14042970","computational-science","docker","reproducible-research","research-management"],"downloads":0},"search_terms":["gotchas","writing","dockerfile","hirokuni"],"keywords":["computational-science","docker","reproducible-research","research-management","*imported-from-citeulike-inrmm","~inrmm-mid:c-14042970"],"authorIDs":[],"dataSources":["5S2zj2hKW8TWTkuMq"]}