big-potato-24262
05/06/2025, 8:18 AMpyflyte register --project lecture-demo --domain development hello_world.py
Running pyflyte register from /Users/motizamir/lecture-demo with images ImageConfig(default_image=Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.12-1.15.4', digest=None), images=[Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.12-1.15.4', digest=None)]) and image destination folder /root on 1 package(s) ('/Users/motizamir/lecture-demo/hello_world.py',)
Registering against localhost:30080
Detected Root /Users/motizamir/lecture-demo, using this to create deployable package...
Loading packages ['hello_world'] under source root /Users/motizamir/lecture-demo
No output path provided, using a temporary directory at /var/folders/y5/y3j823992t1_0lp8t75y_lnh0000gn/T/tmpm_4gg7k8 instead
Code tarball compression took 16 seconds. Consider installing `pigz` for faster compression.
Computed version is bVK-zbKORC2WsIiBwuci7Q
Image <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w> not found. building...
/Users/motizamir/lecture-demo/.venv/lib/python3.12/site-packages/flytekit/image_spec/default_builder.py:196: UserWarning: uv.lock support is experimental
warnings.warn("uv.lock support is experimental", UserWarning)
Run command: docker build --tag <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w> --platform linux/amd64 --push /var/folders/y5/y3j823992t1_0lp8t75y_lnh0000gn/T/tmp5ly4lcvp
[+] Building 4.1s (26/26) FINISHED docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2.11kB 0.0s
=> resolve image config for <docker-image://docker.io/docker/dockerfile:1.5> 1.4s
=> [auth] docker/dockerfile:pull token for <http://registry-1.docker.io|registry-1.docker.io> 0.0s
=> CACHED <docker-image://docker.io/docker/dockerfile:1.5@sha256:39b85bbfa7536a5feceb7372a0817649ecb2724562a38360f4d6a7782a409b14> 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for <http://docker.io/mambaorg/micromamba:2.0.3-debian12-slim|docker.io/mambaorg/micromamba:2.0.3-debian12-slim> 0.8s
=> [internal] load metadata for <http://ghcr.io/astral-sh/uv:0.5.1|ghcr.io/astral-sh/uv:0.5.1> 0.6s
=> [internal] load metadata for <http://docker.io/library/debian:bookworm-slim|docker.io/library/debian:bookworm-slim> 1.0s
=> [auth] mambaorg/micromamba:pull token for <http://registry-1.docker.io|registry-1.docker.io> 0.0s
=> [auth] library/debian:pull token for <http://registry-1.docker.io|registry-1.docker.io> 0.0s
=> [stage-2 1/11] FROM <http://docker.io/library/debian:bookworm-slim@sha256:4b50eb66f977b4062683ff434ef18ac191da862dbe966961bc11990cf5791a8d|docker.io/library/debian:bookworm-slim@sha256:4b50eb66f977b4062683ff434ef18ac191da862dbe966961bc11990cf5791a8d> 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 298.34kB 0.0s
=> [micromamba 1/1] FROM <http://docker.io/mambaorg/micromamba:2.0.3-debian12-slim@sha256:85236af3a2ce605ece8bdd59b0074e0de93638970de16a6d2660c6e4068a5639|docker.io/mambaorg/micromamba:2.0.3-debian12-slim@sha256:85236af3a2ce605ece8bdd59b0074e0de93638970de16a6d2660c6e4068a5639> 0.0s
=> [internal] settings cache mount permissions 0.0s
=> [uv 1/1] FROM <http://ghcr.io/astral-sh/uv:0.5.1@sha256:190cbcca15602bad4531b4310f928fd34a036d50ec3edb6389edc167e21c35b6|ghcr.io/astral-sh/uv:0.5.1@sha256:190cbcca15602bad4531b4310f928fd34a036d50ec3edb6389edc167e21c35b6> 0.0s
=> CACHED [stage-2 2/11] RUN --mount=from=micromamba,source=/etc/ssl/certs/ca-certificates.crt,target=/tmp/ca-certificates.crt [ -f /etc/ssl/certs/ca-certificates 0.0s
=> CACHED [stage-2 3/11] RUN id -u flytekit || useradd --create-home --shell /bin/bash flytekit 0.0s
=> CACHED [stage-2 4/11] RUN chown -R flytekit /root && chown -R flytekit /home 0.0s
=> CACHED [stage-2 5/11] RUN --mount=type=cache,sharing=locked,mode=0777,target=/opt/micromamba/pkgs,id=micromamba --mount=from=micromamba,source=/usr/bin/microma 0.0s
=> CACHED [stage-2 6/11] WORKDIR /root 0.0s
=> CACHED [stage-2 7/11] RUN --mount=type=cache,sharing=locked,mode=0777,target=/root/.cache/uv,id=uv --mount=from=uv,source=/uv,target=/usr/bin/uv --mount=ty 0.0s
=> CACHED [stage-2 8/11] RUN --mount=type=cache,sharing=locked,mode=0777,target=/root/.cache/uv,id=uv --mount=from=uv,source=/uv,target=/usr/bin/uv 0.0s
=> CACHED [stage-2 9/11] WORKDIR /root 0.0s
=> CACHED [stage-2 10/11] RUN mkdir -p $HOME && echo "export PATH=/root/.venv/bin:/opt/micromamba/envs/runtime/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bi 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:09e635ad69236070935025366fa5f73f86fb4ab6423963c5b0fcdb1c46d72f71 0.0s
=> => naming to <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w> 0.0s
=> ERROR pushing <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w> with docker 1.6s
=> => pushing layer a9e59c241eb3 0.7s
=> => pushing layer 5f70bf18a086 0.7s
=> => pushing layer df60449c5013 0.7s
=> => pushing layer fe144b7667a4 0.7s
=> => pushing layer 826f61c93251 0.7s
=> => pushing layer 3ceb7eb05ee9 0.7s
=> => pushing layer e3e7bf216207 0.7s
=> => pushing layer 977f5b1ee0cd 0.7s
=> => pushing layer 6c4c763d22d0 0.7s
------
> pushing <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w> with docker:
------
ERROR: name unknown: repository name not known to registry
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /opt/homebrew/Cellar/python@3.12/3.12.3/Frameworks/Python.framework/Versions/3.12/lib/python3.12 │
│ /subprocess.py:571 in run │
│ │
│ 568 │ │ │ raise │
│ 569 │ │ retcode = process.poll() │
│ 570 │ │ if check and retcode: │
│ ❱ 571 │ │ │ raise CalledProcessError(retcode, process.args, │
│ 572 │ │ │ │ │ │ │ │ │ output=stdout, stderr=stderr) │
│ 573 │ return CompletedProcess(process.args, retcode, stdout, stderr) │
│ 574 │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
CalledProcessError: Command '['docker', 'build', '--tag', '<http://cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w|cr.flyte.org/flyteorg/flyte-sandbox-bundled/say-hello-image:YzWs_2msn0QWwn1bG_fX1w>', '--platform', 'linux/amd64',
'--push', '/var/folders/y5/y3j823992t1_0lp8t75y_lnh0000gn/T/tmp5ly4lcvp']' returned non-zero exit status 1.
Hi @ancient-wolf-19325 can u help me fix that issue?jolly-florist-66728
05/06/2025, 8:18 AMERROR: name unknown: repository name not known to registry
during the docker build --push
step means Docker is trying to push the image to a registry (cr.flyte.org/flyteorg/flyte-sandbox-bundled
) that does not exist or is not accessible from your environment. This is common when using Flyte's local sandbox or demo setup, which does not have a remote registry at that address.
To fix this for local development, you should configure your Flyte project to use a local registry (like localhost:30000
) or avoid the --push
step by using the default image that comes with the sandbox, or by building and tagging images locally without pushing to a remote registry. For more details, see Flyte local setup instructions and ImageSpec registry setup.
Would you like step-by-step instructions on how to configure your registry for local development or how to use a local image with Flyte?
Sources:
- Flyte local setup instructions
- ImageSpec registry setup 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.