Where should I place my bash setup files when using docker?
up vote
1
down vote
favorite
My Dockerfile is below.
Currently I copy the dotfiles (which are referenced within the .bashrc) to /root
Is there a better way to organize them?
FROM alpine:latest
LABEL maintainer="Michael Durrant<junk@snap2web.com>"
RUN apk add bash git vim
COPY alpine_bashrc /root/.bashrc
COPY .bash_functions.sh /root
COPY .bash_aliases /root
COPY .git-completion.bash /root
RUN "/bin/bash"
docker dockerfile
edited Nov 11 at 2:54
eyllanesc
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
add a comment |
up vote
1
down vote
favorite
My Dockerfile is below.
Currently I copy the dotfiles (which are referenced within the .bashrc) to /root
Is there a better way to organize them?
FROM alpine:latest
LABEL maintainer="Michael Durrant<junk@snap2web.com>"
RUN apk add bash git vim
COPY alpine_bashrc /root/.bashrc
COPY .bash_functions.sh /root
COPY .bash_aliases /root
COPY .git-completion.bash /root
RUN "/bin/bash"
docker dockerfile
edited Nov 11 at 2:54
eyllanesc
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My Dockerfile is below.
Currently I copy the dotfiles (which are referenced within the .bashrc) to /root
Is there a better way to organize them?
FROM alpine:latest
LABEL maintainer="Michael Durrant<junk@snap2web.com>"
RUN apk add bash git vim
COPY alpine_bashrc /root/.bashrc
COPY .bash_functions.sh /root
COPY .bash_aliases /root
COPY .git-completion.bash /root
RUN "/bin/bash"
docker dockerfile
edited Nov 11 at 2:54
eyllanesc
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
My Dockerfile is below.
Currently I copy the dotfiles (which are referenced within the .bashrc) to /root
Is there a better way to organize them?
FROM alpine:latest
LABEL maintainer="Michael Durrant<junk@snap2web.com>"
RUN apk add bash git vim
COPY alpine_bashrc /root/.bashrc
COPY .bash_functions.sh /root
COPY .bash_aliases /root
COPY .git-completion.bash /root
RUN "/bin/bash"
docker dockerfile
docker dockerfile
edited Nov 11 at 2:54
eyllanesc
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
edited Nov 11 at 2:54
eyllanesc
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
edited Nov 11 at 2:54
eyllanesc
69.6k93052
edited Nov 11 at 2:54
eyllanesc
69.6k93052
edited Nov 11 at 2:54
eyllanesc
69.6k93052
69.6k93052
asked Nov 11 at 2:52
Michael Durrant
58k65239363
asked Nov 11 at 2:52
Michael Durrant
58k65239363
asked Nov 11 at 2:52
Michael Durrant
58k65239363
58k65239363
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53
add a comment |
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
Instead of having 1 COPY directive for each file, it might be advisable to have a directory instead. The limitation would be that the files must be named as they would appear in the container.
$ ls .
Dockerfile
dotfiles/
.bashrc
.git-completion.bash
.bash_functions.sh
.bash_aliases.sh
Dockerfile
...
COPY dotfiles/ root/
Each of those COPY directives creates a new layer in your container. Save space/time by having one directive.
answered Nov 11 at 3:00
sircapsalot
18.6k65280
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Instead of having 1 COPY directive for each file, it might be advisable to have a directory instead. The limitation would be that the files must be named as they would appear in the container.
$ ls .
Dockerfile
dotfiles/
.bashrc
.git-completion.bash
.bash_functions.sh
.bash_aliases.sh
Dockerfile
...
COPY dotfiles/ root/
Each of those COPY directives creates a new layer in your container. Save space/time by having one directive.
answered Nov 11 at 3:00
sircapsalot
18.6k65280
add a comment |
up vote
3
down vote
Instead of having 1 COPY directive for each file, it might be advisable to have a directory instead. The limitation would be that the files must be named as they would appear in the container.
$ ls .
Dockerfile
dotfiles/
.bashrc
.git-completion.bash
.bash_functions.sh
.bash_aliases.sh
Dockerfile
...
COPY dotfiles/ root/
Each of those COPY directives creates a new layer in your container. Save space/time by having one directive.
answered Nov 11 at 3:00
sircapsalot
18.6k65280
add a comment |
up vote
3
down vote
up vote
3
down vote
Instead of having 1 COPY directive for each file, it might be advisable to have a directory instead. The limitation would be that the files must be named as they would appear in the container.
$ ls .
Dockerfile
dotfiles/
.bashrc
.git-completion.bash
.bash_functions.sh
.bash_aliases.sh
Dockerfile
...
COPY dotfiles/ root/
Each of those COPY directives creates a new layer in your container. Save space/time by having one directive.
answered Nov 11 at 3:00
sircapsalot
18.6k65280
Instead of having 1 COPY directive for each file, it might be advisable to have a directory instead. The limitation would be that the files must be named as they would appear in the container.
$ ls .
Dockerfile
dotfiles/
.bashrc
.git-completion.bash
.bash_functions.sh
.bash_aliases.sh
Dockerfile
...
COPY dotfiles/ root/
Each of those COPY directives creates a new layer in your container. Save space/time by having one directive.
answered Nov 11 at 3:00
sircapsalot
18.6k65280
answered Nov 11 at 3:00
sircapsalot
18.6k65280
answered Nov 11 at 3:00
sircapsalot
18.6k65280
answered Nov 11 at 3:00
sircapsalot
18.6k65280
18.6k65280
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245439%2fwhere-should-i-place-my-bash-setup-files-when-using-docker%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What are you planning to do with the container, such that having a root shell with involved dotfiles is important, and you won't mind when the container is deleted?
– David Maze
Nov 11 at 11:53