This message was deleted.
# ask-for-helps
Slackbot
10/12/2022, 9:01 PMThis message was deleted.
👍 1
🦄 1
👀 1
k
Kim Ted
10/13/2022, 1:54 AMfinding the exact error.
was fine in public network, but as i bring yatai-deployment to private, this shows up. trying to find wheere that image repo is set.
will let u know if i solve it. please let me know if u do, too :)
x
Xipeng Guan
10/13/2022, 3:02 AMThanks for your report! I will add the image builder environment settings feature
👍 2
b
Bharath Krishna
10/13/2022, 2:48 PMHi, thank you for your support, I am facing another issue, in relation to this,
I have taken pod's yaml and added my custom proxy env vars, and deployed it again, both init containers could able to fetch bento and model and the main container,
builderx
Xipeng Guan
10/13/2022, 7:08 PMIt looks like the ubuntu mirror url is not resolved in the pod's container, can you ping the url in the container?
b
Bharath Krishna
10/13/2022, 7:54 PMit was due to proxy env var only,
I set it / exported proxy env vars inside
DockerfileRUN.bashrcBharath Krishna
10/13/2022, 10:29 PMHello, After setting proxy env vars I could able to build image but pushing to registry is failing with 502 as below,
I used these env vars while deploying yatai-deployment,
Copy code
export DOCKER_REGISTRY_SERVER=<http://docker.io|docker.io>
export DOCKER_REGISTRY_USERNAME=username
export DOCKER_REGISTRY_PASSWORD=password
export DOCKER_REGISTRY_SECURE=false
export DOCKER_REGISTRY_BENTO_REPOSITORY_NAME=yatai-bentosBharath Krishna
10/14/2022, 9:16 PMThis above error was due to wrong registry configs and its resolved after fixing it.
I could able to build and push to registry by manually deploying builder pod with custom env vars,
So final requirement is I need someway to pass custom env vars to each containers also, these env vars are required in the Dockerfile's
RUN3 Views