lighthouse-pulse/lcli/Dockerfile

# `lcli` requires the full project to be in scope, so this should be built either:
#  - from the `lighthouse` dir with the command: `docker build -f ./lcli/Dockerflie .`
#  - from the current directory with the command: `docker build -f ./Dockerfile ../`
FROM rust:1.75.0-bullseye AS builder
RUN apt-get update && apt-get -y upgrade && apt-get install -y cmake libclang-dev
COPY . lighthouse
ARG FEATURES
ENV FEATURES $FEATURES
RUN cd lighthouse && make install-lcli

FROM ubuntu:22.04
RUN apt-get update && apt-get -y upgrade && apt-get clean && rm -rf /var/lib/apt/lists/*
COPY --from=builder /usr/local/cargo/bin/lcli /usr/local/bin/lcli
Add lcli Dockerfile and auto-build to CI (#2469) ## Issue Addressed Resolves: #2087 ## Proposed Changes - Add a `Dockerfile` to the `lcli` directory - Add a github actions job to build and push and `lcli` docker image on pushes to `unstable` and `stable` ## Additional Info It's a little awkward but `lcli` requires the full project scope so must be built: - from the `lighthouse` dir with: `docker build -f ./lcli/Dockerflie .` - from the `lcli` dir with: `docker build -f ./Dockerfile ../` Didn't include `libssl-dev` or `ca-certificates`, `lcli` doesn't need these right? Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <micsproul@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> 2021-07-21 03:24:23 +00:00			# `lcli` requires the full project to be in scope, so this should be built either:
			# - from the `lighthouse` dir with the command: `docker build -f ./lcli/Dockerflie .`
			# - from the current directory with the command: `docker build -f ./Dockerfile ../`
Verify Versioned Hashes During Optimistic Sync (#4832) * Convert NewPayloadRequest to use Reference * Refactor for Clarity * Verify Versioned Hashes * Added Tests for Version Hash Verification * Added Moar Tests * Fix Problems Caused By Merge * Update to use Alloy Instead of Reth Crates (#14) * Update beacon_node/execution_layer/src/engine_api/new_payload_request.rs Co-authored-by: realbigsean <seananderson33@GMAIL.com> * Faster Versioned Hash Extraction * Update to rust 1.75 & Pin alloy-consensus 2024-02-18 12:40:45 +00:00			`FROM rust:1.75.0-bullseye AS builder`
upgrade to libp2p 0.52 (#4431) ## Issue Addressed Upgrade libp2p to v0.52 ## Proposed Changes - Workflows: remove installation of `protoc` - Book: remove installation of `protoc` - `Dockerfile`s and `cross`: remove custom base `Dockerfile` for cross since it's no longer needed. Remove `protoc` from remaining `Dockerfiles`s - Upgrade `discv5` to `v0.3.1`: we have some cool stuff in there: no longer needs `protoc` and faster ip updates on cold start - Upgrade `prometheus` to `0.21.0`, now it no longer needs encoding checks - things that look like refactors: bunch of api types were renamed and need to be accessed in a different (clearer) way - Lighthouse network - connection limits is now a behaviour - banned peers no longer exist on the swarm level, but at the behaviour level - `connection_event_buffer_size` now is handled per connection with a buffer size of 4 - `mplex` is deprecated and was removed - rpc handler now logs the peer to which it belongs ## Additional Info Tried to keep as much behaviour unchanged as possible. However, there is a great deal of improvements we can do _after_ this upgrade: - Smart connection limits: Connection limits have been checked only based on numbers, we can now use information about the incoming peer to decide if we want it - More powerful peer management: Dial attempts from other behaviours can be rejected early - Incoming connections can be rejected early - Banning can be returned exclusively to the peer management: We should not get connections to banned peers anymore making use of this - TCP Nat updates: We might be able to take advantage of confirmed external addresses to check out tcp ports/ips Co-authored-by: Age Manning <Age@AgeManning.com> Co-authored-by: Akihito Nakano <sora.akatsuki@gmail.com> 2023-08-02 00:59:34 +00:00			`RUN apt-get update && apt-get -y upgrade && apt-get install -y cmake libclang-dev`
Add lcli Dockerfile and auto-build to CI (#2469) ## Issue Addressed Resolves: #2087 ## Proposed Changes - Add a `Dockerfile` to the `lcli` directory - Add a github actions job to build and push and `lcli` docker image on pushes to `unstable` and `stable` ## Additional Info It's a little awkward but `lcli` requires the full project scope so must be built: - from the `lighthouse` dir with: `docker build -f ./lcli/Dockerflie .` - from the `lcli` dir with: `docker build -f ./Dockerfile ../` Didn't include `libssl-dev` or `ca-certificates`, `lcli` doesn't need these right? Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <micsproul@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> 2021-07-21 03:24:23 +00:00			`COPY . lighthouse`
Make lcli docker image portable (#5069) * Set lcli docker build to use portable feature (#4370) * Merge remote-tracking branch 'origin/unstable' into unstable 2024-01-30 03:03:48 +00:00			`ARG FEATURES`
			`ENV FEATURES $FEATURES`
Add lcli Dockerfile and auto-build to CI (#2469) ## Issue Addressed Resolves: #2087 ## Proposed Changes - Add a `Dockerfile` to the `lcli` directory - Add a github actions job to build and push and `lcli` docker image on pushes to `unstable` and `stable` ## Additional Info It's a little awkward but `lcli` requires the full project scope so must be built: - from the `lighthouse` dir with: `docker build -f ./lcli/Dockerflie .` - from the `lcli` dir with: `docker build -f ./Dockerfile ../` Didn't include `libssl-dev` or `ca-certificates`, `lcli` doesn't need these right? Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <micsproul@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> 2021-07-21 03:24:23 +00:00			`RUN cd lighthouse && make install-lcli`

Use a stable tag for ubuntu in dockerfile (#3231) ## Issue Addressed N/A ## Proposed Changes Use stable version of ubuntu base image in dockerfile instead of using latest. This will help in narrowing down issues with docker images. 2022-05-31 06:09:12 +00:00			`FROM ubuntu:22.04`
Add lcli Dockerfile and auto-build to CI (#2469) ## Issue Addressed Resolves: #2087 ## Proposed Changes - Add a `Dockerfile` to the `lcli` directory - Add a github actions job to build and push and `lcli` docker image on pushes to `unstable` and `stable` ## Additional Info It's a little awkward but `lcli` requires the full project scope so must be built: - from the `lighthouse` dir with: `docker build -f ./lcli/Dockerflie .` - from the `lcli` dir with: `docker build -f ./Dockerfile ../` Didn't include `libssl-dev` or `ca-certificates`, `lcli` doesn't need these right? Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <micsproul@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> 2021-07-21 03:24:23 +00:00			`RUN apt-get update && apt-get -y upgrade && apt-get clean && rm -rf /var/lib/apt/lists/*`
Make lcli docker image portable (#5069) * Set lcli docker build to use portable feature (#4370) * Merge remote-tracking branch 'origin/unstable' into unstable 2024-01-30 03:03:48 +00:00			`COPY --from=builder /usr/local/cargo/bin/lcli /usr/local/bin/lcli`