Here is the latest public version of Rebol 2 (Core) to use with Docker. The purpose of this image is to simplify building the compiler for the Red programming language, that currently depends on it for bootstrapping.

When set up correctly, you will be able to use rebol2-docker command as a drop-in replacement for the usual standalone Rebol executable in all relevant contexts.

There is also a sister repo, describing how to use Red with Docker here.

Build Docker Image
Linux Setup
MacOS Setup
Windows 10 Setup
Usage
Dealing with X11 issues
Running or compiling Red from sources
License

Build Docker Image #

docker build https://codeberg.org/vazub/rebol2-docker.git -t rebol2-docker

Linux Setup #

This was tested on vanilla Pop!_OS 21.04 (64-bit), but should work with minimal adjustment on other distros as well.

Make sure that your X server is installed and echo $DISPLAY shows valid output, for example something like :1 or other number. Then run the following command to fix the access control list:

xhost +local:docker

Now, fix your shell dotfile to have the convenience function to run the image:

echo $'\nfunction rebol2-docker() {\narrVar=()
for arg in "$@"; do
	if 	[[ $arg = -* ]]; then
		arrVar+=($arg)
	else 
		var=$(realpath -eq $arg)
		if
			[[ $var ]]; then
			arrVar+=($var)
		else
			arrVar+=($arg)
		fi	
	fi  
done
	docker run --rm -ti --platform=linux/386 -v /home:/home -v /tmp:/tmp -e DISPLAY=$DISPLAY rebol2-docker ${arrVar[*]}
\n}' >> ~/.bashrc

MacOS Setup #

Install XQuartz and socat. Easiest way is to use Homebrew:

brew update && brew cask install xquartz && brew install socat && brew install coreutils

Starting with macOS Catalina, Macs will now use Zsh as the default login shell and interactive shell across the operating system. That is why we need to create and/or edit .zshrc instead of .bashrc.

echo $'export DISPLAY_MAC=$(ifconfig en0 | grep "inet " | cut -d " " -f2):0' >> ~/.zshrc

echo $'function startx() {\n\tif [ -z "$(ps -ef|grep XQuartz|grep -v grep)" ]; then\n\t\topen -a XQuartz\n\t\tsocat TCP-LISTEN:6000,reuseaddr,fork UNIX-CLIENT:\\\"$DISPLAY\\\" &\n\tfi\n}' >> ~/.zshrc

echo $'\nfunction rebol2-docker() {\narrVar=()
for arg in "$@"; do
	if 	[[ $arg = -* ]]; then
		arrVar+=($arg)
	else 
		var=$(realpath -eq $arg)
		if
			[[ $var ]]; then
			arrVar+=($var)
		else
			arrVar+=($arg)
		fi	
	fi  
done
	docker run --rm -ti --platform=linux/386 -v /Users:/home -v /tmp:/tmp -e DISPLAY=$DISPLAY_MAC rebol2-docker ${arrVar[*]}
\n}' >> ~/.zshrc

source ~/.zshrc

Start XQuartz and socat:

startx

Windows 10 Setup #

This setup flow depends on WSL2 and some X11 server (tested with X410) to be installed and running on the host system.

In PowerShell run wsl to start the default distro

If using WSL versions of distros with Bash shell, run these commands in sequence:

echo $'export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk \'{print $2}\'):0.0' >> ~/.bashrc

echo 'export LIBGL_ALWAYS_INDIRECT=1' >> ~/.bashrc

echo $'\nfunction rebol2-docker() {\narrVar=()
for arg in "$@"; do
	if 	[[ $arg = -* ]]; then
		arrVar+=($arg)
	else 
		var=$(realpath -eq $arg)
		if
			[[ $var ]]; then
			arrVar+=($var)
		else
			arrVar+=($arg)
		fi	
	fi  
done
	docker run --rm -ti --platform=linux/386 -v /home:/home -v /tmp:/tmp -e DISPLAY=$DISPLAY rebol2-docker ${arrVar[*]}
\n}' >> ~/.bashrc

source ~/.bashrc

Working with other default shells should be the same, just replace output redirection in above commants to your shell's session profile.

IMPORTANT: Dockerized Rebol won't currently list files in mounted Widdows paths, so if you want to use it as intended by this particular flow, then keep your project files inside WSL2 distro's filesystem, ex. /home/<user>/<project>.

More WSL2 insights and tips on how to setup your workflow can be found here:

Usage #

Run Rebol with the rebol2-docker command. This will start the REPL. Otherwise, you can use it as a drop-in replacement, to run scripts, like this:

rebol2-docker <your-script>.r

Dealing with X11 Issues #

In case you get some errors that indicate some X11 configuration troubles, check your Windows Firewall settings for the X server you are using. In most cases, the easiest solution would be to delete all specified X server rules and when the firewall asks for new permissions on server restart - make sure allow "Public Network" access. If you use X410, here is a good guide how to check is everything is working as intended.

Running or compiling Red from sources #

This image can be used to run Red programming language scripts or even to compile the language executables themselves from sources.

Clone the Red repo to your machine, go to the repo root folder and run any of the following examples, or build your own commands in similar fashion, as needed:

Compile Linux test script #

rebol2-docker red.r tests/hello.red

Compile Linux CLI console #

rebol2-docker red.r -r environment/console/CLI/console.red

Compile Windows GUI console #

rebol2-docker red.r -r -t Windows environment/console/GUI/gui-console.red

License #

Use of this source code is governed by the MIT-like permissive Blue Oak Model License, an exact copy of which can be found in the relevant LICENSE file of the current repository.

Clone this repository

Rebol with Docker #