you can try running the same command with --no-cac...
# help
b
you can try running the same command with --no-cache and see if the Go base image is pulled.
k
Yes, I tried with --no-cache but getting the same issue
b
Copy code
docker run --rm -it golang:1.15.2-alpine go version
this one works for you?
k
Lemme check
b
if git is running I think the next place to verify is the certificate
in case one of the changes locally is introduction of new module to the system - or even update
Copy code
RUN apk update && apk add --no-cache ca-certificates && update-ca-certificates
add the following after WORKDIR step
if this is the issue I can push a fix
k
I am getting this output go version go1.15.2 linux/amd64
Have I added in the correct place?
Copy code
FROM golang:1.15.2-alpine AS build

ARG VERSION=dev

WORKDIR /build

RUN apk update && apk add --no-cache ca-certificates && update-ca-certificates

# Copy project deps first since they don't change often
COPY go.mod go.sum ./
RUN go mod download
👍 1
Running again...will let u know..
@Barak Amar didn't worked man😅
Same issue
b
share your go.mod and go.sum
better - open an issue and share go.mod, go.sum if they had any change
attached the full output of your docker build
so when we solve this one other people can use our findings
k
Okay I will open the issue
b
Thank you
@kaushal agarwal I think I see the issue
In our project we use OpenAPI (go swagger) - it requires code generation
The docker build assume that all the generated code step is found in workspace
running
make gen
and building the docker or using the makefile's step
build-docker
k
Hey! I think instead there should be an issue raised for adding doc for how to setup local development.😅
b
still can open an issue about the docker - we can address it so other people will not experience the same issue
docs/contributing.md
k
There are many developers who don't have any knowledge of docker. Usually there is a guide as to what steps needs to be followed for locally setting up😅
b
under "Setting up an Environment"
k
Ohh okay😅
b
also referenced from our README
but we can do better - if you had an issue I assume others will have too
will see if making sure that docker build will work from clean env will be a valid solution without making our build time too long
k
Okay I am raising an issue..share the link