Open cforce opened 5 years ago
The same thing happens here. How can we create the config file if the container not started yet ?
The same thing happens here. How can we create the config file if the container not started yet ?
For solve my doubt, i used the docker intellij plugin. There, there is an easy option to point the host_path. In this way i pointed for the folder(folder in windows in my case) that existed my burrow config file.
same here... i find a simple dirty workaround by modifying the Dockerfile:
Dockerfile:
FROM golang:1.12-alpine as builder
ENV BURROW_SRC /usr/src/Burrow/
RUN apk add --no-cache git curl gcc libc-dev
ADD . $BURROW_SRC
WORKDIR $BURROW_SRC
RUN go mod tidy && go build -o /tmp/burrow .
FROM iron/go
LABEL maintainer="LinkedIn Burrow https://github.com/linkedin/Burrow"
WORKDIR /app
COPY --from=builder /tmp/burrow /app/
# Explicitly add the config file
ADD /docker-config/burrow.toml /app/config/burrow.toml
# change the config-dir folder
CMD ["/app/burrow", "--config-dir", "/app/config"]
Just downloaded repo an run docker-compose up -build
but the container burrow_burrow paste the log
Failed reading configuration: Config File "burrow" Not Found in "[/etc/burrow]"
and service does not get available.