DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Related

after installing iRedMail my nginx 404 error
Question
SSL Security (HTTPS) in Django one-click-install configuration
Question

Question

Docker container not running

I’m following this Dockerized Flask App guide with success!

https://www.digitalocean.com/community/tutorials/how-to-build-and-deploy-a-flask-application-using-docker-on-ubuntu-18-04

I am now adapting my own code, and started with two small changes of setting the base image to FROM python:3.7.3-stretch and adding opencv-python==4.4.0.42 as a requirement (I did this as a docker image on my own local machine successfully). On the Droplet, I see that the container is being successfully created but won’t continue to run even though it’s being invoked with a -d argument. Here’s the output:

#docker images
REPOSITORY                   TAG                   IMAGE ID            CREATED             SIZE
nlp.test                     latest                226105eb5bb1        20 minutes ago      1.23GB

root@NLP-FlaskApp-docker-ubuntu-s-1vcpu-2gb-nyc1-01:/var/www/nlpApp# docker run -d -p 56734:80 --name=nlp.test -v $PWD:/app nlp.test
bcb213b1c1ce5e40f29092f0afbcf6b5e1fa1b76e7922a548af806cd9e43dfec
root@NLP-FlaskApp-docker-ubuntu-s-1vcpu-2gb-nyc1-01:/var/www/nlpApp# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

So nothing shows up as running after the command. I also tried running the same command with different port numbers that I checked are open as well as using the start.sh file given in the guide above.

Please let me know of any debug ideas! Thanks

Subscribe
Share
frankieguz • December 25, 2020

Ok, I’ve isolated the issue to the base image used. I changed it back from python-stretch to FROM tiangolo/uwsgi-nginx-flask:python3.6-alpine3.7 and now it continues to stay up after running the start.sh script.

FYI here’s the contents of start.sh:

#!/bin/bash
app="app.test"
docker build -t ${app} .
docker run -d -p 56736:80 \
  --name=${app} \
  -v $PWD:/app ${app}
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev • December 26, 2020

Hi there @frankieguz,

Usually in such cases, what I could suggest is to add the -a argument to the docker ps -a command. That way you will see all of the containers and not just the running ones.

That way you can grab the container ID of the crashing container and check the logs with the docker logs container_id command to get more information on what’s wrong.

Hope that this helps! Regards, Bobby

frankieguz • December 27, 2020

The issue is using Alpine linux, it seems to be incompatible with opencv-python as a requirement.

Also you can’t simply change base images because the one in the guide provides functionality of uwsgi and Nginx

Join the DigitalOcean CommunityCommunity

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner

Related

after installing iRedMail my nginx 404 error
Question
SSL Security (HTTPS) in Django one-click-install configuration
Question

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up