You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the forecaster component, install it in /opt/dfaas-forecaster instead of the root directory (this requires updating the config_constants.py file). In the repository, it should be moved outside the docker directory, as it is a component not directly related to docker. Do not install the dependencies via pip when running as root, use apt instead (or create a virtual environment, see this for how to update the unit file), as it may conflict with the system-wide packages.
Same for the dfaasagent component: it is better to install it in /opt/dfaas-agent instead of /agent, because it is a known directory in FHS. This requires some implementation changes in the agent.
These are some notes about the Dockerfile to build the dfaas node that I collected during some manual deployments:
Use the
hack/install.sh
script provided from faasd, updated with the given version, and not the local one underdocker/files/faasd/hack/install.sh
:dfaas/docker/dfaas-node.dockerfile
Lines 29 to 31 in 034794c
The
faasd
andfaasd-provider
units are already enabled by default when installing faasd using thehack/install.sh
script:dfaas/docker/dfaas-node.dockerfile
Lines 35 to 36 in 034794c
When upgrading cAdvisor to v0.51.0, use the direct link (see release assets) and move the binary to a better location (like
/opt/cadvisor
):dfaas/docker/dfaas-node.dockerfile
Lines 38 to 42 in 034794c
Same issue as the previous point with Prometheus node exporter:
dfaas/docker/dfaas-node.dockerfile
Lines 44 to 48 in 034794c
For the forecaster component, install it in
/opt/dfaas-forecaster
instead of the root directory (this requires updating theconfig_constants.py
file). In the repository, it should be moved outside thedocker
directory, as it is a component not directly related to docker. Do not install the dependencies viapip
when running as root, useapt
instead (or create a virtual environment, see this for how to update the unit file), as it may conflict with the system-wide packages.dfaas/docker/dfaas-node.dockerfile
Lines 61 to 67 in 034794c
Same for the dfaasagent component: it is better to install it in
/opt/dfaas-agent
instead of/agent
, because it is a known directory in FHS. This requires some implementation changes in the agent.dfaas/docker/dfaas-node.dockerfile
Lines 69 to 77 in 034794c
The text was updated successfully, but these errors were encountered: