This message was deleted.
# ask-for-help
s
This message was deleted.
๐Ÿ™Œ 1
๐Ÿฑ 1
t
Probably going to need some more information: What OS are you running on? Is docker installed? Does it get stuck every time? It should start putting out docker output pretty quickly Could you try with --verbose
s
I'm on windows 10. Docker is installed, and the docker destop is on.
b
are you behind a proxy?
s
Before this, I've tried build docker images by following tutorial from docker-curriculum dot com, and it worked
t
what's your version of docker?
Copy code
docker version
s
@Benjamin Tan No proxy in my default web browser, but I enabled Enable DNS over HTTPS
Docker version 20.10.17, build 100c701
b
what did u set the DNS to?
s
Cloudflare
b
1.1.1.1 ?
Try
--verbose
as Tim suggested
s
it's running in verbose now
b
Ah. Can it work if you turn it ofF?
s
I'll try that later. Now it's running the containerize with --verbose
huh it's successful
๐Ÿ‘€ 1
#17 [base-debian 9/10] RUN rm -rf /var/lib/{apt,cache,log} #17 DONE 0.5s #18 [base-debian 10/10] RUN chmod +x /home/bentoml/bento/env/docker/entrypoint.sh #18 DONE 0.5s #19 exporting to image #19 exporting layers #19 exporting layers 3.0s done #19 writing image sha256:aa3703121af2e857a58469f77807d2d6c239eaf97f31a91b80d0efe2b3dd86d3 #19 writing image sha256:aa3703121af2e857a58469f77807d2d6c239eaf97f31a91b80d0efe2b3dd86d3 done #19 naming to docker.io/library/credit_risk_classifier:z4tp2vso56uxtxcb done #19 DONE 3.1s Successfully built docker image for "credit_risk_classifier:z4tp2vso56uxtxcb" with tags "credit_risk_classifier:z4tp2vso56uxtxcb" To run your newly built Bento container, pass "credit_risk_classifier:z4tp2vso56uxtxcb" to "docker run". For example: "docker run -it --rm -p 3000:3000 credit_risk_classifier:z4tp2vso56uxtxcb serve --production". (ml-zoomcamp) C:\Users\husad>
t
๐Ÿ˜ฑ
that's weird...
s
Didn't change anything except adding --verbose
t
does it work without verbose? Like what Ben was asking?
s
How should I check if it works? Delete this docker image first?
Can I just build it the second time?
like, is it gonna overwrite or create another one?
b
if u delete the image it's gonna build from scratch
but i think that's fine.
yeah i think u can delete and do it again
s
it's a success
t
this was after deleting it?
s
yes
t
hmm...
maybe docker desktop was just starting up when you tried it before or something? In a weird state? Or transfering between wifi connections? Something transient?
b
Or maybe it was just harsh words ๐Ÿ˜‰
๐Ÿ˜‚ 1
s
That's a possibility, the docker desktop was on, but only very briefly, maybe just needed more time for it to be ready for bento
a
did docker running as daemon before? I find this often very helpful