SHRED at 12:00, 7 July 2026

2026-07-07T12:00:31Z

← Older revision		Revision as of 14:00, 7 July 2026
Line 82:		Line 82:

	[[Category: Tommi’s to-do list]]		[[Category: Tommi’s to-do list]]
			[[Category:flask]]

Tommi: Add image with graph

2026-04-14T10:18:44Z

Add image with graph

← Older revision		Revision as of 12:18, 14 April 2026
Line 8:		Line 8:

	The de-facto standard to deal with container is [https://docker.com Docker], and it is nearly ubiquitous. Nevertheless, this guide uses [https://podman.io Podman], a drop-in replacement that offers some benefits. This means that at any point of the article and also more in general whenever there is a <code>docker</code> command, it can be replaced with <code>podman</code>, and it should work the same. The reasons behind this choice are beyond the scope of this little guide, but I gathered my notes and thoughts about Podman [https://tommi.space/podman/ in the dedicated page].		The de-facto standard to deal with container is [https://docker.com Docker], and it is nearly ubiquitous. Nevertheless, this guide uses [https://podman.io Podman], a drop-in replacement that offers some benefits. This means that at any point of the article and also more in general whenever there is a <code>docker</code> command, it can be replaced with <code>podman</code>, and it should work the same. The reasons behind this choice are beyond the scope of this little guide, but I gathered my notes and thoughts about Podman [https://tommi.space/podman/ in the dedicated page].

			[[File:Flask container graph.png\|thumb]]

	== Make a Dockerfile ==		== Make a Dockerfile ==

Tommi: Create initial page

2026-04-14T08:26:45Z

Create initial page

New page

Running Flask in a container is tremendously useful to move the same container anywhere and replicate the same exact environment on any device or operating system, without having to modify anything.

== Why a container? ==

A container can be seen a bit like a box with compartments inside it. Running an application (in this case, Flask) on different devices with different operating systems would be like taking different boxes and try to recreate the same compartments inside them, or trying to fit them even if the size of the containing box is not identical. The software equivalent of this would be to install all the dependencies and the required software independently on each device, to try to reach the same result. Using a container would be like taking the original box and move it around, without having to change or adapt its internal structure. Creating a container means that from one device we <q>pack</q> everything that is needed, and then we can ship it (<q>deploy</q> it) anywhere.

== Podman ==

The de-facto standard to deal with container is [https://docker.com Docker], and it is nearly ubiquitous. Nevertheless, this guide uses [https://podman.io Podman], a drop-in replacement that offers some benefits. This means that at any point of the article and also more in general whenever there is a <code>docker</code> command, it can be replaced with <code>podman</code>, and it should work the same. The reasons behind this choice are beyond the scope of this little guide, but I gathered my notes and thoughts about Podman [https://tommi.space/podman/ in the dedicated page].

== Make a Dockerfile ==

The first step is to make a [https://docs.docker.com/build/concepts/dockerfile/ Dockerfile], giving Podman/Docker the <q>instructions</q> to pack the box, which means taking all the software and dependencies necessary to run Flask and place them inside the container.

I have not learned how a Dockerfile actually works (yet). I just made a patchwork of the different Dockerfile examples I found—referenced below.

Here is the essential Dockerfile to run an instance of Flask, block by block.

Download (“pull”) the required images to run the container. In this case, we are pulling Python and [https://docs.astral.sh/uv/ uv], and we are telling Podman to move the executable binaries to specific folders in the container.

<syntaxhighlight lang=Dockerfile>FROM python:3.12-slim-trixie
COPY --from=ghcr.io/astral-sh/uv:0.11 /uv /uvx /bin/</syntaxhighlight>
Assuming that all the files required to run Flask are in <code>./app</code>, we mat them all to <code>/app</code>, inside the container.

<syntaxhighlight lang=Dockerfile># Copy over project files
COPY app/ /app</syntaxhighlight>
Tell the container that we are referring to <code>/app</code> (the directory we just created) whenever we run or do something. In other terms, it is our the working directory of the container.

<syntaxhighlight lang=Dockerfile>WORKDIR /app</syntaxhighlight>
Tell uv to install the required dependencies, listed in <code>pyproject.toml</code>

<syntaxhighlight lang=Dockerfile>RUN uv sync -U</syntaxhighlight>
Flask runs through a specific port. We have to tell the container to <q>expose</q> that port, to make available. This does not mean the port is directly exposed to the outside world, it is just “handed over” and made available to Podman, that can be instructed to actually serve that port (see below).

<syntaxhighlight lang=Dockerfile>EXPOSE 5000</syntaxhighlight>
I couldn’t find a nicer way to do it, but basically this is the final command to be run when the container should be running

<syntaxhighlight lang=Dockerfile>CMD ["uv", "run", "flask", "--app", "main", "run", "--debug", "--host", "0.0.0.0", "--port", "5000"]</syntaxhighlight>
this is the same as running the following in the command line, which is exactly what we are telling the container to do as the last action of the Dockerfile.

<syntaxhighlight lang="bash">uv run flask --app main run --debug --host '0.0.0.0' --port '5000'</syntaxhighlight>
The complete Dockerfile is [https://git.xpub.nl/tommi/flask-intro/src/branch/main/Dockerfile here], in the [https://git.xpub.nl/tommi/flask-intro flask-intro repository].

== Build the container ==

Once the instructions are compiled, the container has to be built. It’s possible to specify which Dockerfile to read, using <code>-f</code>. By default, the reference Dockerfile is <code>Dockerfile</code> in the present working directory.

<syntaxhighlight lang="bash">podman build -t flask-intro:latest # -f Dockerfile</syntaxhighlight>
== Run the container ==

<syntaxhighlight lang="bash">podman run --rm --name flask-intro -p 5000:5000 flask-intro</syntaxhighlight>
== Production vs development mode ==

\#TODO))

== Create Quadlet ==

\#TODO))

== Serve with Caddy ==

\#TODO))

== Resources ==

* [https://medium.com/@brianmayrose/basic-flask-setup-with-podman-6024ba6769e5 Basic Flask Setup With Podman] by Brian Mayrose
* [https://docs.astral.sh/uv/guides/integration/docker/ Using uv in Docker], from the uv documentation
* [https://nickjanetakis.com/blog/switching-pip-to-uv-in-a-dockerized-flask-or-django-app Switching pip to uv in a Dockerized Flask / Django App] by Nick Janetakis
* [https://rest-apis-flask.teclado.com/docs/deploy_to_render/docker_with_gunicorn/ Run our Flask app with gunicorn in Docker | REST APIs with Flask and Python]
* [https://github.com/nickjj/docker-flask-example GitHub - nickjj/docker-flask-example: A production ready example Flask app that's using Docker and Docker Compose. · GitHub]
* [https://testdriven.io/blog/dockerizing-flask-with-postgres-gunicorn-and-nginx/ Dockerizing Flask with Postgres, Gunicorn, and Nginx | TestDriven.io]

{{Youtube|twv_kCq693o}}

{{Youtube|YH9skYpTzxQ}}

{{Youtube|Vlr2q6gWl_Q}}

{{Youtube|KWIIPKbdxD0}}

[[Category: Tommi’s to-do list]]

Flask in a container - Revision history

SHRED at 12:00, 7 July 2026

Tommi: Add image with graph

Tommi: Create initial page