Port details on branch 2024Q4 |
- nomad Cluster manager and scheduler
- 1.9.3 sysutils =5 1.8.1_3Version of this port present on the latest quarterly branch.
- Maintainer: jhixson@FreeBSD.org
- Port Added: 2016-06-22 20:12:21
- Last Update: 2024-12-07 01:59:32
- Commit Hash: a84f289
- People watching this port, also watch:: vault, cbsd, go, zsh, pkg
- License: MPL20
- WWW:
- https://www.nomadproject.io/
- Description:
- Nomad is a cluster manager and scheduler that provides a common workflow
to deploy applications across an infrastructure. Deploy virtualized,
containerized, or standalone application workloads across a fleet of
servers to maximize resource utilization.
- ¦ ¦ ¦ ¦
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- To install the port:
- cd /usr/ports/sysutils/nomad/ && make install clean
- To add the package, run one of these commands:
- pkg install sysutils/nomad
- pkg install nomad
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: nomad
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1733521209
SHA256 (go/sysutils_nomad/hashicorp-nomad-v1.9.3_GH0/go.mod) = 9c01e4fed0d76f5fd11802fa72c6634922a34aaee78e20b91b458c065d0f1657
SIZE (go/sysutils_nomad/hashicorp-nomad-v1.9.3_GH0/go.mod) = 15711
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- go123 : lang/go123
- Fetch dependencies:
-
- go123 : lang/go123
- ca_root_nss>0 : security/ca_root_nss
- This port is required by:
- for Run
-
- sysutils/minipot
- sysutils/nomad-pot-driver
Configuration Options:
- No options to configure
- Options name:
- sysutils_nomad
- USES:
- cpe go:1.23,modules zip
- pkg-message:
- If upgrading
- The nomad rc script requires the nomad data directory (as configured
in the rc variable `nomad_dir`) to use strict directory permissions.
If your nomad data directory was created automatically using a
previous version of the package, it is likely that its permissions
are too lax. If that is the case, nomad will refuse to start with
an error message and the situation can be resolved by adjusting
directory permissions manually by issuing the chmod command,
e.g. `chmod 700 /var/tmp/nomad`.
- Master Sites:
|