uwaru/matterbridge
1
0
Fork 0
forked from jshiffer/matterbridge
Code Pull Requests Activity
v1.22.1
matterbridge/Dockerfile

15 lines
581 B
Docker
Raw Permalink Normal View History

Use alpine stable for docker
2020-09-04 14:47:03 -07:00
FROM alpine AS builder
Add Dockerfile
2016-05-21 07:30:39 -07:00
Optimize Dockerfile (#1361)
2021-01-15 13:44:01 -08:00
COPY . /go/src/matterbridge
RUN apk --no-cache add go git \
&& cd /go/src/matterbridge \
&& go build -mod vendor -ldflags "-X main.githash=$(git log --pretty=format:'%h' -n 1)" -o /bin/matterbridge
Remove build dependencies from final docker image (multistage build) (#1057) This multistage build takes the resulting image size down from 346MB to 90MB.
2020-03-22 14:55:29 -07:00
Use alpine stable for docker
2020-09-04 14:47:03 -07:00
FROM alpine
Remove build dependencies from final docker image (multistage build) (#1057) This multistage build takes the resulting image size down from 346MB to 90MB.
2020-03-22 14:55:29 -07:00
RUN apk --no-cache add ca-certificates mailcap
COPY --from=builder /bin/matterbridge /bin/matterbridge
Combine runs to one layer (#1151)
2020-05-27 15:31:32 -07:00
RUN mkdir /etc/matterbridge \
&& touch /etc/matterbridge/matterbridge.toml \
&& ln -sf /matterbridge.toml /etc/matterbridge/matterbridge.toml
Update Dockerfile so inotify works (#1148) This change would be required for the Docker image to actually read `RELOADABLE` config options from the `matterbridge.toml`. This edit would require https://github.com/42wim/matterbridge/wiki/Deploy:-Docker to be updated as well to mention that mounting would have to change to mounting a ***directory*** not a file. inotify inside Docker cannot read directly mounted files, only directories, for whatever reason. This will preserve setups that were configured to run the old way without breaking them and new configs can be setup "correctly" without issue.
2020-05-24 13:01:52 -07:00
ENTRYPOINT ["/bin/matterbridge", "-conf", "/etc/matterbridge/matterbridge.toml"]
Copy Permalink