blocks|key|1315191|text|Docker构建过程是完全非交互式的，如果您正在寻找一些输入，那么您需要在您的子序列运行命令中传递构建-args和这些构建-args引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1315192|但是，正如推荐中提到的，您需要将它们作为一个CMD运行，因为它会拖住构建过程。|style|CODE|1315193|这里是Dockerfile和一些例子入口点，可能对你有帮助，|1315194|#+start+steamcmd+to+force+it+to+update+itself
RUN+./steamcmd/steamcmd.sh+%2Bquit

#+start+the+server+main+script
ENTRYPOINT+["bash",+"/home/steam/server_scripts/server.sh"]|code-block|syntax|javascript|1315195|你可以把它改成|1315196|/home/steam/steamcmd/steamcmd.sh+\
++++%2Blogin+anonymous+\
++++%2Bexit|1315197|上面列表中的一个例子是cs_go.sh，您需要将它重命名为server.sh|1315198|#!/bin/bash

#+update+server's+data
/home/steam/steamcmd/steamcmd.sh+\
++++%2Blogin+anonymous+\
++++%2Bforce_install_dir+/home/steam/server_data+\
++++%2Bapp_update+740+\
++++%2Bexit

#+start+the+server
/home/steam/server_data/srcds_run+\
++++-game+csgo+-console+-usercon+\
++++-secure+-autoupdate+-tickrate+64+%2Bhostport+27015+\
++++%2Bgame_type+0+%2Bgame_mode+1+%2Bmapgroup+mg_active+%2Bmap+de_dust2+\
++++-port+27015+-console+-secure+-nohltv+%2Bsv_pure+0+%2Bip+0.0.0.0

exit+0|1315199|更新：|BOLD|1315200|自动化SteamCMD|1315201|有两种方法可以使SteamCMD自动化。(在Linux/OS上用./steamcmd.sh替换蒸汽with+)|1315202|命令行|1315203|注意：在命令行上使用-beta选项时，必须以一种特殊的方式引用它，例如%2Bapp_update+"90+-beta+beta“。|1315204|注：，如果这不起作用，试着把它像"%2Bapp_update+90+-beta+beta"一样放上去。|1315205|将命令附加到以加号作为前缀的命令行，例如：|1315206|steamcmd+%2Blogin+anonymous+%2Bforce_install_dir+../csgo_ds+%2Bapp_update+740+%2Bquit|1315207|1315208|entityMap|0|LINK|mutability|MUTABLE|url|https://vsupalov.com/docker-env-vars/|1|https://github.com/respawner/docker-steamcmd|2|https://github.com/respawner/docker-steamcmd/tree/master/scripts|3|https://developer.valvesoftware.com/wiki/SteamCMD^0|1D|7|0|0|M|3|0|3|A|1|E|4|2|0|0|0|0|B|8|T|9|0|0|0|3|0|0|B|0|W|D|0|0|3|0|0|3|Z|B|0|0|2|G|R|0|0|0|0|B|3|0^^$0|@$1|2|3|4|5|6|7|1S|8|@]|9|@$A|1T|B|1U|1|1V]]|C|$]]|$1|D|3|E|5|6|7|1W|8|@$A|1X|B|1Y|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1Z|8|@]|9|@$A|20|B|21|1|22]|$A|23|B|24|1|25]]|C|$]]|$1|J|3|K|5|L|7|26|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|27|8|@]|9|@]|C|$]]|$1|Q|3|R|5|L|7|28|8|@]|9|@]|C|$M|N]]|$1|S|3|T|5|6|7|29|8|@$A|2A|B|2B|F|G]|$A|2C|B|2D|F|G]]|9|@]|C|$]]|$1|U|3|V|5|L|7|2E|8|@]|9|@]|C|$M|N]]|$1|W|3|X|5|6|7|2F|8|@$A|2G|B|2H|F|Y]]|9|@]|C|$]]|$1|Z|3|10|5|6|7|2I|8|@$A|2J|B|2K|F|Y]]|9|@]|C|$]]|$1|11|3|12|5|6|7|2L|8|@$A|2M|B|2N|F|G]]|9|@]|C|$]]|$1|13|3|14|5|6|7|2O|8|@$A|2P|B|2Q|F|Y]]|9|@]|C|$]]|$1|15|3|16|5|6|7|2R|8|@$A|2S|B|2T|F|Y]|$A|2U|B|2V|F|G]]|9|@]|C|$]]|$1|17|3|18|5|6|7|2W|8|@$A|2X|B|2Y|F|Y]|$A|2Z|B|30|F|G]]|9|@]|C|$]]|$1|19|3|1A|5|6|7|31|8|@]|9|@]|C|$]]|$1|1B|3|1C|5|L|7|32|8|@]|9|@]|C|$M|N]]|$1|1D|3|10|5|6|7|33|8|@]|9|@$A|34|B|35|1|36]]|C|$]]|$1|1E|3|-4|5|6|7|37|8|@]|9|@]|C|$]]]|1F|$1G|$5|1H|1I|1J|C|$1K|1L]]|1M|$5|1H|1I|1J|C|$1K|1N]]|1O|$5|1H|1I|1J|C|$1K|1P]]|1Q|$5|1H|1I|1J|C|$1K|1R]]]]

The Docker build process is completely non-interactive, and if you are looking for some input then you need to pass <a href="https://vsupalov.com/docker-env-vars/" rel="nofollow noreferrer">build-args</a>, and the reference these build-args in your sub-sequent RUN command.

But as mentioned in the commend you need to run them as a <code>CMD</code> as it will stuck the build process.

Here is <a href="https://github.com/respawner/docker-steamcmd" rel="nofollow noreferrer">Dockerfile</a> with <a href="https://github.com/respawner/docker-steamcmd/tree/master/scripts" rel="nofollow noreferrer">some example</a> entrypoint that may help you,

<pre><code># start steamcmd to force it to update itself
RUN ./steamcmd/steamcmd.sh +quit

# start the server main script
ENTRYPOINT ["bash", "/home/steam/server_scripts/server.sh"]
</code></pre>

You can change it to

<pre><code>/home/steam/steamcmd/steamcmd.sh \
 +login anonymous \
 +exit
</code></pre>

and one example from above list is <code>cs_go.sh</code> which you need to rename to <code>server.sh</code> is

<pre><code>#!/bin/bash

# update server's data
/home/steam/steamcmd/steamcmd.sh \
 +login anonymous \
 +force_install_dir /home/steam/server_data \
 +app_update 740 \
 +exit

# start the server
/home/steam/server_data/srcds_run \
 -game csgo -console -usercon \
 -secure -autoupdate -tickrate 64 +hostport 27015 \
 +game_type 0 +game_mode 1 +mapgroup mg_active +map de_dust2 \
 -port 27015 -console -secure -nohltv +sv_pure 0 +ip 0.0.0.0

exit 0
</code></pre>

updated:

Automating SteamCMD

There are two ways to automate SteamCMD. (Replace steamcmd with <code>./steamcmd.sh</code> on Linux/OS X.)

Command line

Note: When using the -beta option on the command line, it must be quoted in a special way, such as <code>+app_update</code> "90 -beta beta".

Note: If this does not work, try putting it like <code>"+app_update 90 -beta beta"</code> instead.

Append the commands to the command line prefixed with plus characters, e.g.:

<pre><code>steamcmd +login anonymous +force_install_dir ../csgo_ds +app_update 740 +quit
</code></pre>

<a href="https://developer.valvesoftware.com/wiki/SteamCMD" rel="nofollow noreferrer">Automating SteamCMD</a>

I am trying to use Valve's <code>steamcmd</code> package in a bash script, an interactive shell that takes user input. Of course i'd like to be able to send input manually as part of a docker build, but I'm running into some issues.

I started by installing <code>steamcmd</code> locally and running this script:

<pre class="lang-sh prettyprint-override"><code>./steamcmd &lt;&lt;LOGIN
login anonymous
quit
LOGIN
</code></pre>

Unsurprisingly, it works properly, yielding this output:

<pre><code>Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
Steam&gt;
</code></pre>

The problems start when I try the same command in Docker:

<pre><code>RUN ./steamcmd &lt;&lt;LOGIN \
login anonymous \
quit \
LOGIN
</code></pre>

During the build, it runs <code>./steamcmd</code> but then hangs on the input prompt, none of the data in the Heredoc is passed and the build never completes. What am I doing wrong?

Extra Info:

<ul>
<li>Base Image: <code>ubuntu:latest</code></li>
<li>User: non root</li>
</ul>

Bash Heredoc doesn't seem to work with Docker RUN statement

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我试图使用阀门的steamcmd包在一个bash脚本，一个交互式的外壳，接受用户的输入。当然，我希望能够手动发送输入，作为对接构建的一部分，但我遇到了一些问题。我首先在本地安装steamcmd并运行以下脚本：./steamcmd <<LOGINlogin anonymousquitLOGIN不出所料，它工作正常，产生了...

问Bash似乎不适用于Docker语句
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Bash似乎不适用于Docker语句EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Bash似乎不适用于Docker语句
EN