brl/citadel
1
0
Fork 2
Code Issues Pull Requests 2 Packages Projects Releases Wiki Activity
Subgraph Citadel image builder
75 Commits 2 Branches 0 Tags 18 MiB
BitBake 88.3%
Shell 7.6%
Makefile 1.1%
HTML 0.9%
Vim Script 0.9%
Other 0.9%
ae9eb5e2a0
Go to file
Bruce Leidl ae9eb5e2a0 hardcoded /etc/machine-id 
Otherwise systemd will bind-mount tmpfs on this file and generate a new
machine-id on each boot.  This causes persistent journal to not
work correctly.
2018-02-18 12:56:04 -05:00
meta-citadel hardcoded /etc/machine-id 2018-02-18 12:56:04 -05:00
meta-citadel-distro big refactor of how state is handled on /storage 2018-02-17 17:44:33 -05:00
meta-foreign removed 2018-01-18 18:26:39 -05:00
meta-intel Merge commit '5789f1b122ac5b32dce85e80a36dafe049c757cd' as 'meta-intel' 2017-12-04 16:35:46 -05:00
meta-rust@17cc34c9c8 import meta-rust layer as submodule 2018-02-12 22:21:52 -05:00
poky Merge commit '098b8f982b61f2bd11c170d2e9eefce90bd7736b' as 'poky' 2017-12-04 16:35:29 -05:00
scripts added some packages and a logind.conf setting 2018-02-12 22:18:16 -05:00
.gitignore initial commit 2017-12-04 16:33:20 -05:00
.gitmodules import meta-rust layer as submodule 2018-02-12 22:21:52 -05:00
Makefile added a makefile target to update git submodules 2018-02-13 10:32:31 -05:00
README.md added a makefile target to update git submodules 2018-02-13 10:32:31 -05:00
setup-build-env don't change the shell prompt 2018-02-03 10:24:39 -05:00

README.md

Building Citadel

Set up Docker

Building citadel requires that you have Docker CE installed on the build host. The version of Docker provided by your Linux distribution will probably not work and you should follow the following instructions instead:

After installing Docker you may need to start the docker daemon.

$ systemctl start docker

If you want the docker daemon to start automatically on boot you also need to enable it.

$ systemctl enable docker

You may optionally add your user account to the docker group so that you can issue docker commands without using sudo.

Warning: This is more convenient but be careful because containers can be configured to share any file on the host. A user with access to the docker group can easily escalate privileges to root while the docker daemon is running.

$ sudo usermod -aG docker $USER

Building with Docker

A Makefile is provided which only contains a couple of simple targets that execute docker commands to set up and run the builder container.

The project uses git submodules to track openembedded layers it depends upon. After cloning this repository you will need to retrieve the dependent submodules with the following command:

$ make update-submodules

To create the builder docker image use the following command. You only need to do this one time, but if you run it again Docker will realize that the Dockerfile has not changed and do nothing.

$ make docker-image

To list available make targets, run make help or just make as this is the default target:

$ make help

To run a shell inside the docker build container:

$ make docker-shell

The shell will run in the build directory and be configured to run build commands with bitbake.

To build a full citadel image:

$ make citadel-image

The build will take several hours the first time, but for later builds the build system will use cached artifacts stored in citadel/build/sstate-cache for components that have not changed and new builds will usually only take a few minutes.