This repository contains a bash script and Dockerfile that will pull and build the Fabric Attached Memory packages necessary for running code on The Machine, FAME (Fabric Attached Memory Emulation), and various SuperDome products. These packages are all in Github under the Fabric Attached Memory organization.

This build container has been tested and verified working on the following operating systems :

• Red Hat Enterprise Linux 7.3
• Ubuntu 17.04
• Fedora 26
• Debian Jessie and Stretch

This repository should be cloned and built locally.

If you are behind a corporate firewall, Docker needs to know. This article explains it all.

Clone and build the repository with:

git clone [email protected]:FabricAttachedMemory/l4fame-build-container.git
cd l4fame-build-container && docker build --tag l4fame-build .

If you're behind a firewall and have the standard environment variables set, add

--build-arg http_proxy=$http_proxy --build-arg https_proxy=$https_proxy

to the arguments.

Once the Docker image has been built it needs to be run. First create an empty directory in $HOME to hold the results:

mkdir -m777 $HOME/theDebs

Run the container:

docker run -t --name l4fame-build --privileged -v ~/theDebs:/debs -v L4FAME_BUILD:/build l4fame-build

If you're behind a firewall and have the standard environment variables set, add

--env http_proxy=$http_proxy --env https_proxy=$https_proxy

to the arguments.

To disconnect from the container without killing it, type Ctrl+C in the window in which you executed "docker run ..."

To reconnect to the container run docker attach l4fame-builder

Some environment variables can be added to the "docker run" command with the "-e variable=value" syntax:

To completely remove the container:

docker stop l4fame-build
docker rm l4fame-build
docker rmi l4fame-build

To remove the source repos and build artifacts:

docker volume rm L4FAME_BUILD

On completion ~/theDebs should contain all the packages necessary for running code in a FAME environment, on a SuperDome Flex global memory environment, or The Machine itself (ARM).

At the top level will be all the packages and a directory called "logs". Under logs is one file per built package, making it easy to troubleshoot build problems. There is also a file named "00_mainloop.log", a global catchall for builder.bash flow. These files are only created if builder.bash was enabled for AMD (the default).

If you have enabled builder.bash for ARM (the default), you'll see a another directory under theDebs, "arm64". Under there is a similar structure: all the debs plus a "log" directory with multiple files as described above.

Instructions for building individual packages can be found here

This project is licensed under the MIT License - see the LICENSE file for details