blocks|key|2087545|text|基本上像往常一样，将其添加到用户的.bashrc文件中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2087546|FROM+foo
RUN+echo+'alias+hi="echo+hello"'+>>+~/.bashrc|code-block|syntax|javascript|2087547|像往常一样，这只适用于交互式shell：|2087548|docker+build+-t+test+.
docker+run+-it+--rm+--entrypoint+/bin/bash+test+hi
/bin/bash:+hi:+No+such+file+or+directory
docker+run+-it+--rm+test+bash
$+hi
hello|2087549|对于非交互式shell，您应该创建一个小脚本并将其放入路径中，即：|2087550|RUN+echo+-e+'#!/bin/bash\necho+hello'+>+/usr/bin/hi+&&+\
++++chmod+%2Bx+/usr/bin/hi|2087551|如果您的别名使用参数(即hi+Jim+->+hello+Jim)，只需添加"$@"|2087552|RUN+echo+-e+'#!/bin/bash\necho+hello+"$@"'+>+/usr/bin/hi+&&+\
++++chmod+%2Bx+/usr/bin/hi|2087553|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Bash_(Unix_shell)#Legacy-compatible_Bash_startup_example^0|H|7|H|7|0|0|0|0|0|0|0|C|6|M|9|11|4|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|U|3|V|5|H|7|1M|8|@]|D|@]|E|$I|J]]|$1|W|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

Basically like you always do, by adding it to the user's <a href="https://en.wikipedia.org/wiki/Bash_(Unix_shell)#Legacy-compatible_Bash_startup_example" rel="nofollow noreferrer"><code>.bashrc</code></a> file:
<pre class="lang-none prettyprint-override"><code>FROM foo
RUN echo 'alias hi=&quot;echo hello&quot;' &gt;&gt; ~/.bashrc
</code></pre>
As usual this will only work for interactive shells:
<pre class="lang-none prettyprint-override"><code>docker build -t test .
docker run -it --rm --entrypoint /bin/bash test hi
/bin/bash: hi: No such file or directory
docker run -it --rm test bash
$ hi
hello
</code></pre>
For non-interactive shells you should create a small script and put it in your path, i.e.:
<pre class="lang-none prettyprint-override"><code>RUN echo -e '#!/bin/bash\necho hello' &gt; /usr/bin/hi &amp;&amp; \
 chmod +x /usr/bin/hi
</code></pre>
If your alias uses parameters (ie. <code>hi Jim</code> -&gt; <code>hello Jim</code>), just add <code>&quot;$@&quot;</code>:
<pre class="lang-none prettyprint-override"><code>RUN echo -e '#!/bin/bash\necho hello &quot;$@&quot;' &gt; /usr/bin/hi &amp;&amp; \
 chmod +x /usr/bin/hi
</code></pre>

blocks|key|2087621|text|要创建现有命令的别名，还可以使用ln+-s|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2087622|ln+-s+$(which+<existing_command>)+/usr/bin/<my_command>|code-block|syntax|javascript|2087623|entityMap^0|G|5|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

To create an alias of an existing command, might also use <code>ln -s</code>:
<pre class="lang-none prettyprint-override"><code>ln -s $(which &lt;existing_command&gt;) /usr/bin/&lt;my_command&gt;
</code></pre>

blocks|key|2087671|text|如果您只想在Dockerfile中使用别名，而不想在容器中使用别名，那么最短的方法就是ENV+declaration|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2087672|ENV+update='apt-get+update+-qq'
ENV+install='apt-get+install+-qq'

RUN+$update+&&+$install+apt-utils+\
++++curl+\
++++gnupg+\
++++python3.6|code-block|syntax|javascript|2087673|对于容器中的使用，就像前面描述的那样：|2087674|+RUN+printf+'#!/bin/bash+\n+$(which+apt-get)+install+-qq+$@'+>+/usr/bin/install
+RUN+chmod+%2Bx+/usr/bin/install|2087675|大多数时候，我只是在构建阶段使用别名，而不是进入容器内部，因此第一个示例更快、更清晰、更简单，便于日常使用。|2087676|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/builder/#env^0|17|3|17|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|17|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If you want to use aliases just in Dockerfile, but not inside a container then the shortest way is the <a href="https://docs.docker.com/engine/reference/builder/#env" rel="nofollow noreferrer"><code>ENV</code> declaration</a>:
<pre><code>ENV update='apt-get update -qq'
ENV install='apt-get install -qq'

RUN $update &amp;&amp; $install apt-utils \
 curl \
 gnupg \
 python3.6
</code></pre>
And for use in a container the way like already described:
<pre><code> RUN printf '#!/bin/bash \n $(which apt-get) install -qq $@' &gt; /usr/bin/install
 RUN chmod +x /usr/bin/install
</code></pre>
Most of the time I use aliases just in the building stage and do not go inside containers, so the first example is quicker, clearer and simpler for every day use.

blocks|key|2087726|text|我刚刚将以下代码添加到我的app.dockerfile文件中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2087727|#+Set+up+aliases
ADD+./bashrc_alias.sh+/usr/sbin/bashrc_alias.sh
ADD+./initbash_profile.sh+/usr/sbin/initbash_profile
RUN+chmod+%2Bx+/usr/sbin/initbash_profile
RUN+/bin/bash+-C+"/usr/sbin/initbash_profile"|code-block|syntax|javascript|2087728|在initbash_profile.sh文件中，它只附加了我的自定义别名，不需要获取文件的源文件：|2087729|#+Add+the+Bash+aliases
cat+/usr/sbin/bashrc_alias.sh+>>+~/.bashrc|2087730|这真是太棒了！|2087731|另一种选择是从容器外部使用"docker+exec+-it命令“，并且只使用您自己的.bashrc或.bash_profile文件(无论您喜欢什么)。|2087732|例如，|2087733|docker+exec+-it+docker_app_1+bash|2087734|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I just added this to my app.dockerfile file:
<pre><code># Set up aliases
ADD ./bashrc_alias.sh /usr/sbin/bashrc_alias.sh
ADD ./initbash_profile.sh /usr/sbin/initbash_profile
RUN chmod +x /usr/sbin/initbash_profile
RUN /bin/bash -C &quot;/usr/sbin/initbash_profile&quot;
</code></pre>
And inside the initbash_profile.sh file which just appends my custom aliases and no need to source the <a href="https://en.wikipedia.org/wiki/Bash_(Unix_shell)#Legacy-compatible_Bash_startup_example" rel="nofollow noreferrer">.bashrc</a> file:
<pre><code># Add the Bash aliases
cat /usr/sbin/bashrc_alias.sh &gt;&gt; ~/.bashrc
</code></pre>
It worked a treat!
Another option is to just use the &quot;docker exec -it &lt;container-name&gt; command&quot; from outside the container and just use your own .bashrc or the .bash_profile file (what ever you prefer).
E.g.,
<pre class="lang-none prettyprint-override"><code>docker exec -it docker_app_1 bash
</code></pre>

blocks|key|1873654|text|您可以在Dockerfile文件中使用ENTRYPOINT，但它不适用于别名：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1873655|ADD+dev/entrypoint.sh+/opt/entrypoint.sh
ENTRYPOINT+["/opt/entrypoint.sh"]|code-block|syntax|javascript|1873656|您的entrypoint.sh文件：|style|CODE|1873657|#!/bin/bash
set+-e

function+dev_run()
{

}

export+-f+dev_run

exec+"$@"|1873658|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/builder/#entrypoint^0|J|A|0|0|0|2|D|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

You can use <a href="https://docs.docker.com/engine/reference/builder/#entrypoint" rel="nofollow noreferrer">ENTRYPOINT</a>, but it will not work for aliases, in your Dockerfile:
<pre><code>ADD dev/entrypoint.sh /opt/entrypoint.sh
ENTRYPOINT [&quot;/opt/entrypoint.sh&quot;]
</code></pre>
Your <code>entrypoint.sh</code> file:
<pre><code>#!/bin/bash
set -e

function dev_run()
{

}

export -f dev_run

exec &quot;$@&quot;
</code></pre>

blocks|key|1873804|text|我认为最简单的方法是将一个包含别名的文件挂载到容器中，然后指定Bash应该在哪里找到它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1873805|docker+run+\
++++-it+\
++++--rm+\
++++-v+~/.bash_aliases:/tmp/.bash_aliases+\
++++[image]+\
++++/bin/bash+--init-file+/tmp/.bash_aliases|code-block|syntax|javascript|1873806|示例用法：|1873807|echo+'alias+what="echo+it+works"'+>+my_aliases
docker+run+-it+--rm+-v+~/my_aliases:/tmp/my_aliases+ubuntu:18.04+/bin/bash+--init-file+/tmp/my_aliases
alias|1873808|输出：|1873809|alias+what='echo+it+works'|1873810|what|1873811|1873812|it+works|1873813|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|Q|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

I think the easiest way would be to mount a file into your container containing your aliases, and then specify where Bash should find it:
<pre><code>docker run \
 -it \
 --rm \
 -v ~/.bash_aliases:/tmp/.bash_aliases \
 [image] \
 /bin/bash --init-file /tmp/.bash_aliases
</code></pre>
Sample usage:
<pre class="lang-none prettyprint-override"><code>echo 'alias what=&quot;echo it works&quot;' &gt; my_aliases
docker run -it --rm -v ~/my_aliases:/tmp/my_aliases ubuntu:18.04 /bin/bash --init-file /tmp/my_aliases
alias
</code></pre>
Output:
<pre class="lang-none prettyprint-override"><code>alias what='echo it works'
</code></pre>
<pre class="lang-none prettyprint-override"><code>what
</code></pre>
Output:
<pre><code>it works
</code></pre>

blocks|key|1873922|text|使用了以前的一些解决方案，但仍无法识别别名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1873923|我正在尝试设置别名，并在以后的Dockerfile步骤中和运行时在容器中使用它们。|1873924|RUN+echo+"alias+model-downloader='python3+${MODEL_DL_PATH}/downloader.py'"+>>+~/.bash_aliases+&&+\
++++echo+"alias+model-converter='python3+${MODEL_DL_PATH}/converter.py'"+>>+~/.bash_aliases+&&+\
++++source+~/.bash_aliases

#+Download+the+model
RUN+model-downloader+--name+$MODEL_NAME+-o+$MODEL_DIR+--precisions+$MODEL_PRECISION;|code-block|syntax|javascript|1873925|对我来说，解决方案是使用保存文件夹路径的ENV变量，然后添加确切的可执行文件。我也可以使用ARG，但在我的更多场景中，我需要在构建阶段和稍后的运行时中使用别名。|1873926|我将ENV变量与一个Bash脚本结合使用，该脚本在依赖项填充后运行，并设置Bash源，设置一些更多的环境变量，并允许通过管道传递更多命令。|1873927|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Used some of the previous solutions, but the aliases are not recognised still.
I'm trying to set aliases and use them both within later Dockerfile steps and in the container at runtime.
<pre><code>RUN echo &quot;alias model-downloader='python3 ${MODEL_DL_PATH}/downloader.py'&quot; &gt;&gt; ~/.bash_aliases &amp;&amp; \
 echo &quot;alias model-converter='python3 ${MODEL_DL_PATH}/converter.py'&quot; &gt;&gt; ~/.bash_aliases &amp;&amp; \
 source ~/.bash_aliases

# Download the model
RUN model-downloader --name $MODEL_NAME -o $MODEL_DIR --precisions $MODEL_PRECISION;
</code></pre>
The solution for me was to use ENV variables that held folder paths and then add the exact executable. I could have use ARG too, but for more of my scenarios I needed the aliases in both the build stage and later in the runtime.
I used the ENV variables in conjunction with a Bash script that runs once dependencies have ponged and sets the Bash source, sets some more env variables, and allows for further commands to pipe through.

blocks|key|2087974|text|下面是一个Bash函数，它可以将您的别名放在您交互使用的每个容器中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2087975|ducker_it()+{
++++docker+cp+~/bin/alias.sh+"$1":/tmp
++++docker+exec+-it+"$1"+/bin/bash+-c+"[[+!+-f+/tmp/alias.sh.done+]]+\
++++++++&&+[[+-w+/root/.bashrc+]]+\
++++++++&&+cat+/tmp/alias.sh+>>+/root/.bashrc+\
++++++++&&+touch+/tmp/alias.sh.done"
++++docker+exec+-it+"$1"+/bin/bash
}|code-block|syntax|javascript|2087976|在此之前的必需步骤：|2087977|grep+%5Ealias+~/.zshrc+>+~/bin/alias.sh|2087978|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here is a Bash function to have your aliases in every container you use interactively.
<pre><code>ducker_it() {
 docker cp ~/bin/alias.sh &quot;$1&quot;:/tmp
 docker exec -it &quot;$1&quot; /bin/bash -c &quot;[[ ! -f /tmp/alias.sh.done ]] \
 &amp;&amp; [[ -w /root/.bashrc ]] \
 &amp;&amp; cat /tmp/alias.sh &gt;&gt; /root/.bashrc \
 &amp;&amp; touch /tmp/alias.sh.done&quot;
 docker exec -it &quot;$1&quot; /bin/bash
}
</code></pre>
Required step before:
<pre><code>grep ^alias ~/.zshrc &gt; ~/bin/alias.sh
</code></pre>

I am new to Docker. I found that we can set environment variables using the ENV instruction in the Dockerfile. But how does one set Bash aliases for long commands in Dockerfile?

How can I set Bash aliases for docker containers in Dockerfile?

容器

Docker

我是Docker的新手。我发现我们可以使用Dockerfile中的ENV指令来设置环境变量。但是如何在Dockerfile中为长命令设置Bash别名呢？

问如何在Dockerfile中为docker容器设置Bash别名？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Dockerfile中为docker容器设置Bash别名？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Dockerfile中为docker容器设置Bash别名？
EN