osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
9
0
Fork 0
Code Releases Activity
docker-playground/osmo-nitb-master/Dockerfile

55 lines
1.7 KiB
Docker
Raw Normal View History

Fix "'laforge/debian-jessie-build' not found" Instead of hardcoding laforge's username in all FROM statements in the Dockerfiles, make use of the USER variable (as passed through by the "make/Makefile" with "docker build --build-arg USER=..."). Thanks to fixeria for proposing this fix! This requires running docker-ce, old versions of docker (such as the one in the official repositories of the latest Fedora) don't support variables in the FROM line. But docker-ce can be installed after adding docker's 3rd party repositories. Closes: OS#3457 Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
2018-09-05 11:12:13 +00:00
ARG USER
Switch all osmo-*-master and ttcn3-*-test from jessie to stretch Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2019-03-27 11:31:48 +00:00
FROM $USER/debian-stretch-build
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
MAINTAINER Harald Welte <laforge@gnumonks.org>
Switch all osmo-*-master and ttcn3-*-test from jessie to stretch Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2019-03-27 11:31:48 +00:00
ARG OSMOCOM_REPO="http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_9.0/"
osmo-*: Ensure container is rebuilt if nightly repo is updated Let's use the "ADD" trick that we use for git repositories also for the osmocom:nightly debian package feed. This way any change to the package feed will result in a rebuild of the container.
2017-12-17 10:48:54 +00:00
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
COPY Release.key /tmp/Release.key
RUN apt-key add /tmp/Release.key && \
rm /tmp/Release.key && \
osmo-*: Ensure container is rebuilt if nightly repo is updated Let's use the "ADD" trick that we use for git repositories also for the osmocom:nightly debian package feed. This way any change to the package feed will result in a rebuild of the container.
2017-12-17 10:48:54 +00:00
echo "deb " $OSMOCOM_REPO " ./" > /etc/apt/sources.list.d/osmocom-nightly.list
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
osmo-*-master: Invalidate docker cache when CentOS repo changes We currently only invalidate the cache if the Debian repository changes, but not if the CentOS repository changes. This leads to strange artefacts, such as CentOS containers for osmo-bts-master using an old libosmocore, despite a new one being available in the repo. As Dockerfiles don't support conditional "ADD", we need to actually add both the CentOS and the Debian repsotiry file, so any change in either of the two will now (unneccessarily) invalidate the cache for both Debian and CentOS builds. Change-Id: I7b13644afb9d3be3b94184193177e003c13718d3
2020-10-16 11:10:08 +00:00
# we need to add this to invalidate the cache once the repository is updated.
# unfortunately Dockerfiles don't support a conditional ARG, so we need to add both DPKG + RPM
osmo-*: Ensure container is rebuilt if nightly repo is updated Let's use the "ADD" trick that we use for git repositories also for the osmocom:nightly debian package feed. This way any change to the package feed will result in a rebuild of the container.
2017-12-17 10:48:54 +00:00
ADD $OSMOCOM_REPO/Release /tmp/Release
osmo-*-master: Invalidate docker cache when CentOS repo changes We currently only invalidate the cache if the Debian repository changes, but not if the CentOS repository changes. This leads to strange artefacts, such as CentOS containers for osmo-bts-master using an old libosmocore, despite a new one being available in the repo. As Dockerfiles don't support conditional "ADD", we need to actually add both the CentOS and the Debian repsotiry file, so any change in either of the two will now (unneccessarily) invalidate the cache for both Debian and CentOS builds. Change-Id: I7b13644afb9d3be3b94184193177e003c13718d3
2020-10-16 11:10:08 +00:00
ADD http://download.opensuse.org/repositories/network:/osmocom:/nightly/CentOS_8_Stream/repodata/repomd.xml /tmp/repomd.xml
apt-get: always use --no-install-recommends and apt-get clean this helps us to avoid installing unneeded packages and removes the package cache from the images to keep them less bloated.
2017-08-27 07:53:26 +00:00
RUN apt-get update && \
apt-get install -y --no-install-recommends \
telnet \
libosmocore-dev \
libosmo-abis-dev \
libosmo-netif-dev \
libosmo-sccp-dev \
libsmpp34-dev \
Fix Dockerfile syntax error in apt-get command
2017-08-28 05:46:41 +00:00
libgtp-dev && \
apt-get: always use --no-install-recommends and apt-get clean this helps us to avoid installing unneeded packages and removes the package cache from the images to keep them less bloated.
2017-08-27 07:53:26 +00:00
apt-get clean
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
WORKDIR /tmp
Add OSMO_*_BRANCH environment variables for build args Previously we could only set OSMO_TTCN3_BRANCH as environment variable to build a test other than master. This patch adds environment variables for all osmo-*-master images which allow docker tests to be executed for an arbitrary commit. The origin/ prefix from the git checkout command is removed so the *_BRANCH variable doesn't have to contain branch names, but van also contain arbitrary commits. This shouldn't have any adverse effect as we only have one remote in the checkout. Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
2019-04-25 11:56:14 +00:00
ARG OSMO_NITB_BRANCH="master"
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
RUN git clone git://git.osmocom.org/openbsc.git
Add OSMO_*_BRANCH environment variables for build args Previously we could only set OSMO_TTCN3_BRANCH as environment variable to build a test other than master. This patch adds environment variables for all osmo-*-master images which allow docker tests to be executed for an arbitrary commit. The origin/ prefix from the git checkout command is removed so the *_BRANCH variable doesn't have to contain branch names, but van also contain arbitrary commits. This shouldn't have any adverse effect as we only have one remote in the checkout. Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
2019-04-25 11:56:14 +00:00
ADD http://git.osmocom.org/openbsc/patch?h=$OSMO_NITB_BRANCH /tmp/commit-openbsc
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
RUN cd openbsc/openbsc && \
Fix git checkout for branches and commits Replace 'git checkout -f -B $BRANCH origin/$BRANCH && \' in all Dockerfiles that accept branch variables ($OSMO_TTCN3_BRANCH, $OSMO_MGW_BRANCH, ...) with the following: git checkout $BRANCH && \ (git symbolic-ref -q HEAD && git reset --hard origin/$BRANCH || exit 1); \ This allows using branch names and commit hashes in the $BRANCH variables. Using commits is needed for the bisect script added in [1]. The second line ("(git symbolic...") checks if we are in detached HEAD state after the checkout, and if we are not, pulls in all new commits from origin/$BRANCH. Note that it ends in ';' instead of '&&', because the command in the next line should be executed even if "git symbolic-ref" does not exit with 0 (detached HEAD state). Here is an example, to illustrate that the new command does the right thing. Clone a repository and be 50 commits behind origin/master: $ git clone "https://git.osmocom.org/osmo-mgw" $ cd osmo-mgw $ git reset --hard origin/master~50 With BRANCH="master": $ git checkout master && \ (git symbolic-ref -q HEAD && git reset --hard origin/master || exit 1); \ echo "done" Already on 'master' ... done $ git status Your branch is up-to-date with 'origin/master'. With BRANCH="85978d": $ git checkout 85978d && \ (git symbolic-ref -q HEAD && git reset --hard origin/85978d || exit 1); \ echo "done" Note: checking out '85978d'. ... done $ git status HEAD detached at 85978dad Related previous changes: * [2] made it work for commit hashes, but broke using branch names other than master, and pulling in new commits from master * [3] made branches other than master work again, but did not fix pulling in new commits from master * [4] reverted [3] and the git checkout related part from [2] [1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f [2] Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869 [3] Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3 [4] Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25 Related: OS#4015 Change-Id: I4004980baf0b7d6096702b6f3067ccbdb369a28c
2019-05-22 07:08:25 +00:00
git fetch && git checkout $OSMO_NITB_BRANCH && \
(git symbolic-ref -q HEAD && git reset --hard origin/$OSMO_NITB_BRANCH || exit 1); \
Add OSMO_*_BRANCH environment variables for build args Previously we could only set OSMO_TTCN3_BRANCH as environment variable to build a test other than master. This patch adds environment variables for all osmo-*-master images which allow docker tests to be executed for an arbitrary commit. The origin/ prefix from the git checkout command is removed so the *_BRANCH variable doesn't have to contain branch names, but van also contain arbitrary commits. This shouldn't have any adverse effect as we only have one remote in the checkout. Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
2019-04-25 11:56:14 +00:00
git rev-parse --abbrev-ref HEAD && git rev-parse HEAD && \
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
autoreconf -fi && \
./configure --enable-nat --enable-osmo-bsc --enable-smpp && \
make: use $(nproc) instead of hard-coded number of cores Change-Id: Ie93b81a8a9206c47c4e4d4834fc5c03d9bf4254c
2020-07-12 19:51:58 +00:00
make "-j$(nproc)" install && \
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
ldconfig
VOLUME /data
COPY openbsc.cfg /data/openbsc.cfg
osmo-nitb-master: Add default config file for osmo-bsc_nat Change-Id: I44bb395009582f5e1399f277e15203553c2dcf78 Related: OS#1700
2019-06-19 11:25:22 +00:00
COPY osmo-bsc-nat.cfg /data/osmo-bsc-nat.cfg
COPY bscs.config /data/bscs.config
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
WORKDIR /data
Update osmo-*/Dockerfile to log stdout+stderr of process to log file This way we get VTY parsing failures as well as backtraces upon process crash. Related: OS#4212 Change-Id: I9493ff73ef27c7c6d32b00cf827704b3f9cbf86a
2019-11-13 14:26:45 +00:00
CMD ["/bin/sh", "-c", "/usr/local/bin/osmo-nitb -c /data/osmo-nitb.cfg >/data/osmo-nitb.log 2>&1"]
add Dockerfiles for osmo-nitb, osmo-sgsn + osmo-bts building latest master
2017-08-20 18:19:13 +00:00
EXPOSE 3002/tcp 3003/tcp 4242/tcp 2775/tcp 4249/tcp