hi @mozzymutesa
I get this persistent error on accessing the instance after starting the containers.
am I missing anything?
did it run fine previously before your changes ??
can you paste the server side logs here with pastebin??
occured after pulling the latest changes, that is those of docker hub registry
Looks like you have a Liquibase error .
In case you don’t have any liquibase change locally ,
can you delete you db container volumes and start a fresh ??
1 Like
on it! thanks @Moses_Mutesasira
which docker-compose file are you running ??
dev.docker(for mounting locally compiled artifacts)… is this what you wanted?
@Moses_Mutesasira this error has persisted even on fresh conatiners
which command have you ran to clear the volumes ??
sudo docker stop ccba7992b2a4 eadf4095ec30 bc5b799544ae 37c8f8de1466 a5e170959183 1ce1dc882b60
sudo docker rm ccba7992b2a4 eadf4095ec30 bc5b799544ae 37c8f8de1466 a5e170959183 1ce1dc882b60
Run docker-compose -f dev.docker-compose.yml down -v
can you also run mvn clean install and ensure your tests pass locally ??
1 Like
on running mvn clean install log: mvn clean install - Pastebin.com
you do not have docker running
running mvn clean install as root user, with fingers crossed 
sudo mvn clean install
threw this error terminal output
then I did
git submodule update --init --recursivecd dataexportmvn clean install
on running mvn install, it builds with success but with liquibase like warnings or errors
curiously ran
docker-compose -f dev.docker-compose.yml up -d
but the instance only shows a blank white screen…
did you try docker-compose -f dev.docker-compose.yml down -v. before spinning up the containers again ??
Ive just tested it now on a remote machine and it runs fine .
Try the steps
-
Clean the volumes
docker-compose -f dev.docker-compose.yml down -v -
Ensure you pulled the latest code changes
-
Ensure you don’t have any breaking change in the java source code
-
Try spinning up the containers again
docker-compose -f dev.docker-compose.yml up -d