DevOps

Here we document errors (and solutions) with the DevOps tooling. Each will be documented in the following format:

# Concise, primary error message (e.g. "Permission Denied")

## Error

Copy-and-pasted full error message in a code block (three ticks open, three ticks close)

## Reproduction

Description of the commands given and/or steps taken to reproduce the error

## Solution

Description and step-by-step instructions for the solution. If a commit has been made and merged to the primary branch, also link to the commit.

Couldn't find an integrity file

Error

When starting the container using docker compose on Windows or Linux, we get the error:

codewitus-web-1  | error Couldn't find an integrity file
codewitus-web-1  | error Found 1 errors.

Solution

We have a workaround by running tabularasa.sh which deletes the yarn.lock file. Note: tabularasa.sh rebuilds the container as a blank slate (tabula rasa).

Linux no file/dir error on Windows

Error

When using docker-compose up on Windows OS, we can get the following error:

codewitus-web-1  | standard_init_linux.go:228: exec user process caused: no such file or directory
codewitus-web-1 exited with code 1

Solution

Use dos2unix to convert entrypoint.sh from Linux encoding to Windows. If you use VS Code, you can do this by clicking on the bottom right on CRLF and change it to LF.

Cannot start service db

When running docker-compose up, the following error message (or similar) is produced, which prevents the container from running. This error is replicated on Linux Mint 20.

Error

Starting codewitus_db_1 ... error

ERROR: for codewitus_db_1  Cannot start service db: driver failed programming external connectivity on endpoint codewitus_db_1 (bab44778dfb1ef330daf151496500faf9c87e603844684c687270cb7b836d65b): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use

ERROR: for db  Cannot start service db: driver failed programming external connectivity on endpoint codewitus_db_1 (bab44778dfb1ef330daf151496500faf9c87e603844684c687270cb7b836d65b): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Solution

The port is already active, in this case 5432. To kill the process using the port, use the following command:

sudo lsof -ti:5432 | xargs sudo kill -9

After doing so, the port should be available for use so try running the container again.

pg_stat_tmp/global.stat Permission denied

Error

When launching the Docker container, there are numerous errors and warnings including:

could not open statistics file "pg_stat_tmp/global.stat": Permission denied

And they seem to repeat endlessly.

Solution

First, terminate the process (using Ctrl+C). Run your command again without the sudo command. For example, sudo sh tabularasa.sh may cause the error, but sh tabularasa.sh should not.