I am having my build failing today with the below. I am not too sure why this is the case. Is there any suggested troubleshooting I can do?
==> Pushing image to fly
100
The push refers to repository [registry.fly.io/vetrx-app-development]
101
d438812530b1: Preparing
102
e03b72389f0b: Preparing
103
...
112
e4fc34115d04: Waiting
113
0baa13659589: Waiting
114
74f7cf53c3a5: Waiting
115
8573f1735336: Waiting
116
afbcd854ab4c: Waiting
117
9c1b6dd6c1e6: Waiting
118
Error failed to fetch an image or build from source: error rendering push status stream: unauthorized: not allowed
1 Like
This is on our end. We were performing emergency maintenance on the registry and the deployment took longer than expected. It should be done now, let us know if you see any more issues.
Seems to working on now, thanks!
1 Like
frafra
May 16, 2022, 10:46pm
#4
I can confirm this happens from time to time. Running flyctl deploy again fixes that.
I’m experiencing this issue after uninstalling and reinstalling the CLI:
❯ fly deploy
==> Verifying app config
--> Verified app config
==> Building image
Remote builder fly-builder-rough-sun-5961 ready
==> Creating build context
--> Creating build context done
==> Building image with Docker
--> docker host: 20.10.12 linux x86_64
[+] Building 4.1s (0/1)
[+] Building 1.6s (11/11) FINISHED
=> [internal] load remote build context 0.0s
=> copy /context / 0.4s
=> [internal] load metadata for docker.io/library/python:3.7 0.1s
=> [1/7] FROM docker.io/library/python:3.7@sha256:11c044f967935362ef8291811ed01b0708a40668c43c8 0.0s
=> CACHED [2/7] RUN apt-get update && apt-get install -y python3-pip python3-venv p 0.0s
=> CACHED [3/7] RUN mkdir -p /app 0.0s
=> CACHED [4/7] WORKDIR /app 0.0s
=> CACHED [5/7] COPY requirements.txt . 0.0s
=> CACHED [6/7] RUN pip install -r requirements.txt 0.0s
=> [7/7] COPY . . 0.4s
=> exporting to image 0.4s
=> => exporting layers 0.4s
=> => writing image sha256:ba4c850eb788d3bf272efc515c2f67f01e66a90267e5be3290e3a1c5dd7ec6d6 0.0s
=> => naming to registry.fly.io/justrecipe:deployment-1653615561 0.0s
--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/justrecipe]
f66f68f9ff4f: Preparing
22c7b3c7d04d: Preparing
056d54c04b13: Preparing
5f70bf18a086: Preparing
7752ae6b5fd7: Preparing
00800d747256: Waiting
2e0764ceda8b: Waiting
3f5d38b4936d: Waiting
7be8268e2fb0: Waiting
b889a93a79dd: Waiting
9d4550089a93: Waiting
a7934564e6b9: Waiting
1b7cceb6a07c: Waiting
b274e8788e0c: Waiting
78658088978a: Waiting
Error failed to fetch an image or build from source: error rendering push status stream: unauthorized: not allowed
We are running into the same issue now.
We are noticing this as well!
mwills
May 27, 2022, 8:07am
#10
Ah not just me.
[edit] ah it just worked!
[edit 2] mostly… pulling an image fails occasionally at the moment.
1 Like
Sorry for the trouble. This is related to an ongoing incident with AWS DNS resolution. We thought it was fixed, but it’s come back.
2 Likes
We’ve applied a fix for this and are monitoring closely.
2 Likes
frafra
June 3, 2022, 10:06pm
#15
It still happens from time to time.
It’s still happening for me as well sometimes.
cake4
June 30, 2022, 2:43pm
#17
I get this error consistently when trying to deploy via Github Actions using superfly/flyctl-actions . From my local machine, the build and deployment (–remote-only) works just fine, even when using the same API token. Any ideas?
For those seeing this issue - which regions are you located in?
kris1
September 3, 2022, 11:42pm
#20
@jsierles - experiencing this issue just now in the SYD region!
Yaeger
September 26, 2022, 9:55am
#21
We are getting this error right now:
Error failed to fetch an image or build from source: error rendering push status stream: unauthorized: not allowed
Region was ams, it’s working now again.
