Andras Fekete 93f865f2d4 Use proper capitalization 4 weeks ago
..
OpenWrt ca73a311cf Don't use /dev/null 1 year ago
packaging 7a12202675 Init deb packaging 1 year ago
wolfCLU 93f865f2d4 Use proper capitalization 4 weeks ago
yocto 1c68da282c portability enhancement: use "#!/usr/bin/env <interpreter>" on all perl scripts and shell scripts that use bash extensions, and use "#!/bin/sh" on the rest. 4 months ago
Dockerfile cf6975b603 Add less frequently used tools that are handy to have 1 month ago
Dockerfile.cross-compiler 5e85adee0f Add yet another cross compiling tool 8 months ago
README.md 2ef83e142f Update buildAndPush.sh and README.md 1 year ago
buildAndPush.sh 1c68da282c portability enhancement: use "#!/usr/bin/env <interpreter>" on all perl scripts and shell scripts that use bash extensions, and use "#!/bin/sh" on the rest. 4 months ago
include.am 9fdb3cf17a Appease test scripts 1 year ago
run.sh 1c68da282c portability enhancement: use "#!/usr/bin/env <interpreter>" on all perl scripts and shell scripts that use bash extensions, and use "#!/bin/sh" on the rest. 4 months ago

README.md

Overview

This is a Docker environment for compiling, testing and running WolfSSL. Use run.sh to build everything (Docker container, WolfSSL, etc.). This script takes in arguments that can be passed to ./configure. For example: run.sh --enable-all

When the compilation and tests succeed, you will be dropped in to a shell environment within the container. This can be useful to build other things within the environment. Additional tests can be run as well as debugging of code.

Docker Hub

These images are also uploaded to the wolfSSL's Docker Hub page. There is a convenience script here buildAndPush.sh that will create the appropriate containers and push them to the repo.

FAQ

permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock

You need to be added to the docker group to run Docker containers. Run sudo usermod -aG docker $USER. You may need to restart the Docker daemon.

Unable to access symlinked files outside of WolfSSL

The volume mounted in the Docker container needs to have all files that your compilation will need. To solve this, you have a couple options:

  1. Change the WOLFSSL_DIR variable in the run.sh to one higher up (by adding /.. to the path). Then update the docker build to include the correct path to the Dockerfile and the docker run argument to the working directory (-w) to the WolfSSL source directory
  2. Move the external repository to within the WolfSSL directory. For example create an external folder which has your files. This route may have complications when stashing Git work.