Skip to content

Commit

Permalink
[docker] don't set m3dbnode binary caps in build (#1672)
Browse files Browse the repository at this point in the history
  • Loading branch information
schallert authored May 29, 2019
1 parent 3c4fd5a commit c982091
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 9 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Changelog

# 0.9.6

## Bug Fixes

- **M3DB**: Revert Docker setcap change to allow image to run with no special flags (#1672)

# 0.9.5

## Performance
Expand Down
9 changes: 0 additions & 9 deletions docker/m3dbnode/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -26,14 +26,5 @@ COPY --from=builder /go/src/github.com/m3db/m3/bin/m3dbnode /bin/
COPY --from=builder /go/src/github.com/m3db/m3/src/dbnode/config/m3dbnode-local-etcd.yml /etc/m3dbnode/m3dbnode.yml
COPY --from=builder /go/src/github.com/m3db/m3/scripts/m3dbnode_bootstrapped.sh /bin/

# Use setcap to set +e "effective" and +p "permitted" to adjust the
# SYS_RESOURCE so the process can raise the hard file limit with
# setrlimit
RUN apk add libcap && \
setcap cap_sys_resource=+ep /bin/m3dbnode

# Set the environment variable to raise the limit on startup
ENV PROCESS_LIMITS_RAISE true

ENTRYPOINT [ "/bin/m3dbnode" ]
CMD [ "-f", "/etc/m3dbnode/m3dbnode.yml" ]

0 comments on commit c982091

Please sign in to comment.