blocks|key|525798|text|当我忘记运行heroku+container:login时，我遇到了这个问题。即使您登录到heroku，heroku容器服务也需要单独登录。这就是为什么你在上传一开始就得到了正确的错误--你没有被授权。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|525799|entityMap^0|6|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had this problem when I forgot to run <code>heroku container:login</code>. Even if you're logged in to heroku, heroku container service requires a separate login. That's why you're getting the error right at the beginning of the upload - you are not authorised.

blocks|key|525767|text|我需要显式地传递应用程序名称，而不是内部名称，所以heroku+container:push+--app+rocky-wildwood-86034运行得很顺利。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|525768|我做到了:+heroku容器:push+--app+mediabox|525769|合适的是:+heroku容器:push+--app+rocky-wildwood-86034|525770|简单应用程序名称应该是全局heroku应用程序名称，而不是docker-compose.yml中定义的名称。|525771|entityMap^0|P|1C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|S|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|M|$]]

I needed to explicitly pass the app name and not the internal one so doing <code>heroku container:push --app rocky-wildwood-86034</code> went well.

I did:
heroku container:push --app mediabox

the proper one was:
heroku container:push --app rocky-wildwood-86034

Simple the app name should be the global heroku app name instead of the one which was defined in docker-compose.yml.

blocks|key|517060|text|当我第一次忘记heroku+container:login时，我也遇到了同样的错误。不确定您的问题是否由相同的用户错误引起。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|517061|entityMap^0|7|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had the same error when I forgot to <code>heroku container:login</code> first. Not sure if your problem was caused by the same user error.

blocks|key|3628206|text|网站注册.heroku.com/mediabox/+|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3628207|blockquote|3628208|3628209|3628210|只要使用heroku仪表板创建一个名为'mediabox‘的应用程序，并再次尝试推送图像，它对我来说是有效的。|3628211|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|-4|5|C|7|K|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|I|$]]

<blockquote>
 registry.heroku.com/mediabox/web
</blockquote>

Just to create an app with name 'mediabox' by using of heroku dashboard and try again to push image, it works for me.

blocks|key|3628261|text|遵循Heroku文档(https://devcenter.heroku.com/articles/container-registry-and-runtime#logging-in-to-the-registry)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3628262|3628263|Login：首先，检查您是否已登录。|ordered-list-item|style|BOLD|3628264|3628265|3628266|+docker登录--用户名=您的用户--密码=$(heroku身份验证:令牌)+registry.heroku.com|blockquote|3628267|3628268|3628269|或|3628270|3628271|+heroku容器:登录|3628272|3628273|3628274|对接镜像：执行heroku+cli或|3628275|Push命令。|3628276|3628277|3628278|+heroku容器:推流IMG_NAME|3628279|3628280|3628281|3628282|3628283|+docker标签注册表.heroku.com/APP/IMG_NAME|3628284|3628285|docker推流registry.heroku.com/APP/IMG_NAME|3628286|3628287|3628288|请注意，应用程序(上面的应用程序)必须存在于Heroku仪表板上。|3628289|3628290|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/container-registry-and-runtime#logging-in-to-the-registry^0|B|2N|0|0|0|0|5|0|0|0|0|0|0|0|0|0|0|0|0|0|7|0|0|0|0|K|0|0|0|0|1|0|0|0|10|0|0|0|14|0|0|0|0|X|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@$A|1S|B|1T|1|1U]]|C|$]]|$1|D|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1W|8|@$A|1X|B|1Y|H|I]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|20|8|@]|9|@]|C|$]]|$1|L|3|M|5|N|7|21|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|22|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|23|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|24|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|25|8|@]|9|@]|C|$]]|$1|T|3|U|5|N|7|26|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|27|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|28|8|@]|9|@]|C|$]]|$1|X|3|Y|5|6|7|29|8|@]|9|@]|C|$]]|$1|Z|3|10|5|G|7|2A|8|@$A|2B|B|2C|H|I]]|9|@]|C|$]]|$1|11|3|-4|5|6|7|2D|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|2E|8|@]|9|@]|C|$]]|$1|13|3|14|5|N|7|2F|8|@$A|2G|B|2H|H|I]]|9|@]|C|$]]|$1|15|3|-4|5|6|7|2I|8|@]|9|@]|C|$]]|$1|16|3|-4|5|6|7|2J|8|@]|9|@]|C|$]]|$1|17|3|R|5|6|7|2K|8|@$A|2L|B|2M|H|I]]|9|@]|C|$]]|$1|18|3|-4|5|6|7|2N|8|@]|9|@]|C|$]]|$1|19|3|1A|5|N|7|2O|8|@$A|2P|B|2Q|H|I]]|9|@]|C|$]]|$1|1B|3|-4|5|6|7|2R|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|6|7|2S|8|@$A|2T|B|2U|H|I]]|9|@]|C|$]]|$1|1E|3|-4|5|6|7|2V|8|@]|9|@]|C|$]]|$1|1F|3|-4|5|6|7|2W|8|@]|9|@]|C|$]]|$1|1G|3|1H|5|G|7|2X|8|@$A|2Y|B|2Z|H|I]]|9|@]|C|$]]|$1|1I|3|-4|5|6|7|30|8|@]|9|@]|C|$]]|$1|1J|3|-4|5|6|7|31|8|@]|9|@]|C|$]]]|1K|$1L|$5|1M|1N|1O|C|$1P|1Q]]]]

Following the Heroku documentation (<a href="https://devcenter.heroku.com/articles/container-registry-and-runtime#logging-in-to-the-registry" rel="nofollow noreferrer">https://devcenter.heroku.com/articles/container-registry-and-runtime#logging-in-to-the-registry</a>):
<ol>
<li>Login: First of all, check if you're logged in.</li>
</ol>
<blockquote>
docker login --username=YOUR_USER --password=$(heroku auth:token)
registry.heroku.com
</blockquote>
Or
<blockquote>
heroku container:login
</blockquote>
<ol start="2">
<li>Push the image: Execute the heroku cli or docker command.</li>
</ol>
<blockquote>
heroku container:push IMG_NAME
</blockquote>
Or
<blockquote>
docker tag registry.heroku.com/APP/IMG_NAME
docker push registry.heroku.com/APP/IMG_NAME
</blockquote>
<ol start="3">
<li>Notice that the application (APP above) must exist on Heroku dashboard.</li>
</ol>

blocks|key|516961|text|首先，正如你所链接的文章所说，在Heroku中的Docker集成还处于测试阶段。它可能仍然有一些bug。因此，直接联系Heroku的支持人员也许是个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|516962|假设Heroku集成和你的代码都没问题，我只能建议你停止使用heroku+container:push，只使用官方的docker命令。这可能会避免一些推送问题。|offset|length|style|CODE|516963|您可以使用以下命令在本地构建镜像：|516964|docker+build+.+|code-block|syntax|javascript|516965|然后使用以下命令将其推送到Heroku：|516966|docker+tag+<image>+registry.heroku.com/<app>/<process-type>
docker+push+registry.heroku.com/<app>/<process-type>|516967|我有使用Docker的基于Gitlab+CI和Heroku的生产环境。我们的所有集成只依赖于docker命令，并且我们从未遇到过在本地推送镜像的任何问题。|516968|entityMap^0|0|U|L|0|0|0|0|0|1A|6|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

First of all, Docker integration in Heroku is in BETA, as the article you linked says. It may still have some bugs. So maybe is a good idea to contact directly the Heroku support on this.

Assuming Heroku integration and your code are both OK, I can only suggest you to stop using <code>heroku container:push</code> and use only the official docker commands. This may avoid some pushing issues.

You can build the image locally using: 

<pre><code>docker build . 
</code></pre>

Then push it to Heroku using:

<pre><code>docker tag &lt;image&gt; registry.heroku.com/&lt;app&gt;/&lt;process-type&gt;
docker push registry.heroku.com/&lt;app&gt;/&lt;process-type&gt;
</code></pre>

I have production environments based on Gitlab CI and Heroku using Docker. All our integration depends only on <code>docker</code> commands, and we have never experienced any issues with pushing images built locally.

I was following the this article <a href="https://devcenter.heroku.com/articles/container-registry-and-runtime" rel="noreferrer">https://devcenter.heroku.com/articles/container-registry-and-runtime</a> and I'm stuck with "heroku container:push". I run "heroku container:push --app mediabox" and the docker image is properly build and then it start to push it to registry and this is what I get:

<pre><code>Successfully built 7926b98d51b5
The push refers to a repository [registry.heroku.com/mediabox/web]
38d48dd6de30: Preparing 
969058e6ddc9: Preparing 
2f454953e0e7: Preparing 
f67c1ecd32a1: Preparing 
44fade3982ca: Preparing 
0accb1c81980: Waiting 
e79bbdfaa0d3: Waiting 
1be5d1797b73: Waiting 
5c0a4f4b3a35: Waiting 
011b303988d2: Waiting 
error parsing HTTP 400 response body: unexpected end of JSON input: ""
 ! Error: docker push exited with 1
</code></pre>

This is my Dockerfile:

<pre><code>FROM ruby:2.3.1-alpine

RUN apk --update --no-cache add build-base less libxml2-dev libxslt-dev nodejs postgresql-dev &amp;&amp; mkdir -p /app

WORKDIR /app

COPY Gemfile Gemfile.lock ./

RUN gem install bundler

RUN bundle

COPY . ./

CMD ["script/docker-entrypoint.sh"]
</code></pre>

I can't find the solution here. Thanks for your help.

Heroku docker deployment

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我一直在关注这篇文章，我坚持使用"heroku容器:推送“。我运行"heroku container:push --app mediabox“，docker镜像被正确构建，然后它开始将其推送到注册表，这是我得到的结果：Successfully built 7926b98d51b5The push refers to a repository [registry.heroku.com/mediabo

问Heroku docker部署
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Heroku docker部署EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Heroku docker部署
EN