status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/scripts/package_src/nimbus_beacon_node/after_install

28 lines
638 B
Plaintext
Raw Permalink Normal View History

use Bourne shell as the actual postinst script does (#4638) The `postinst` wrapper script into which these scripts are embedded as `after_upgrade` and `after_install` functions are executed using Bourne shell(`sh`), so we cannot use the Bash specific `[[ ]]` test or it fails: ``` /var/lib/dpkg/info/nimbus-beacon-node.postinst: 22: [[: not found ``` Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-17 12:13:28 +00:00
#!/bin/sh
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended.
2021-12-07 13:23:57 +00:00
set -e
drop dependency on lsb-release script (#4597) The `/etc/os-release` file exists in most distributions and can be easily read in Bash by sourcing it: ``` > docker run --rm -it debian:bullseye root@2f5d6e038738:/# grep '^ID=' /etc/os-release ID=debian ``` ``` > docker run --rm -it ubuntu:22.04 root@316b572b6e4d:/# grep '^ID=' /etc/os-release ID=ubuntu ``` The dependency on `lsb-release` tool is unnecessary, and pulls in additional big dependencies like `python3`: ``` # apt show lsb-release | grep Depends Depends: python3:any, distro-info-data ``` Which if used in a Docker container would make it unnecessarily big. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-06 10:43:24 +00:00
DISTRO="UNKNOWN"
use Bourne shell as the actual postinst script does (#4638) The `postinst` wrapper script into which these scripts are embedded as `after_upgrade` and `after_install` functions are executed using Bourne shell(`sh`), so we cannot use the Bash specific `[[ ]]` test or it fails: ``` /var/lib/dpkg/info/nimbus-beacon-node.postinst: 22: [[: not found ``` Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-17 12:13:28 +00:00
if [ -r /etc/os-release ]; then
after_install: use . not source in bourne shell (#4639) Another dumb mistake when using bourne shell: ``` /var/lib/dpkg/info/nimbus-beacon-node.postinst: 23: source: not found ``` Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-17 13:26:23 +00:00
. /etc/os-release
drop dependency on lsb-release script (#4597) The `/etc/os-release` file exists in most distributions and can be easily read in Bash by sourcing it: ``` > docker run --rm -it debian:bullseye root@2f5d6e038738:/# grep '^ID=' /etc/os-release ID=debian ``` ``` > docker run --rm -it ubuntu:22.04 root@316b572b6e4d:/# grep '^ID=' /etc/os-release ID=ubuntu ``` The dependency on `lsb-release` tool is unnecessary, and pulls in additional big dependencies like `python3`: ``` # apt show lsb-release | grep Depends Depends: python3:any, distro-info-data ``` Which if used in a Docker container would make it unnecessarily big. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-06 10:43:24 +00:00
DISTRO="${ID}"
fi
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended.
2021-12-07 13:23:57 +00:00
if ! id -u nimbus > /dev/null 2>&1; then
case $DISTRO in
drop dependency on lsb-release script (#4597) The `/etc/os-release` file exists in most distributions and can be easily read in Bash by sourcing it: ``` > docker run --rm -it debian:bullseye root@2f5d6e038738:/# grep '^ID=' /etc/os-release ID=debian ``` ``` > docker run --rm -it ubuntu:22.04 root@316b572b6e4d:/# grep '^ID=' /etc/os-release ID=ubuntu ``` The dependency on `lsb-release` tool is unnecessary, and pulls in additional big dependencies like `python3`: ``` # apt show lsb-release | grep Depends Depends: python3:any, distro-info-data ``` Which if used in a Docker container would make it unnecessarily big. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-06 10:43:24 +00:00
Ubuntu|ubuntu|Debian|debian)
packaging updates (#3974) * packaging updates * one package per binary (nimbus_beacon_node, nimbus_validator_client) * use `-` in package name (`_` is separating the version) * don't include (un)installation scripts in package * default metrics port 8108 for vc * fix several upgrade/install errors in scripts * add JWT option to service files * don't attempt to remove user on purge
2022-08-17 10:26:31 +00:00
# Debian uses `adduser` to create user...
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended.
2021-12-07 13:23:57 +00:00
adduser --system --no-create-home --group nimbus
;;
packaging updates (#3974) * packaging updates * one package per binary (nimbus_beacon_node, nimbus_validator_client) * use `-` in package name (`_` is separating the version) * don't include (un)installation scripts in package * default metrics port 8108 for vc * fix several upgrade/install errors in scripts * add JWT option to service files * don't attempt to remove user on purge
2022-08-17 10:26:31 +00:00
*)
# ... while `useradd` is more standard
useradd --system --no-create-home --user-group nimbus
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended.
2021-12-07 13:23:57 +00:00
;;
esac
fi
mkdir -p /var/lib/nimbus
chown nimbus:nimbus /var/lib/nimbus
ignore systemctl failure in after_install scripts (#4596) Otherwise installation in Docker containers fails with: ``` ... Adding new user `nimbus' (UID 101) with group `nimbus' ... Not creating home directory `/home/nimbus'. /var/lib/dpkg/info/nimbus-beacon-node.postinst: 39: systemctl: not found dpkg: error processing package nimbus-beacon-node (--configure): installed nimbus-beacon-node package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: nimbus-beacon-node E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-02-06 10:01:57 +00:00
# Systems like docker containers do not have systemd.
systemctl daemon-reload || echo "notice: systemd daemon not reloaded" >&2