AWS上でDockerコンテナとApacheを用いたFlaskアプリケーションのデプロイ

ウェブ開発

はじめに

DockerとFlaskを活用して軽量で効率的なウェブアプリケーション環境を構築する方法について、この記事では詳しく解説します。Dockerは、その隔離性と移植性により、開発者がさまざまなアプリケーションを簡単かつ迅速にデプロイできるようにする画期的なツールです。一方、FlaskはPythonで書かれた軽量なウェブフレームワークで、そのシンプルさと拡張性により、迅速なウェブアプリケーション開発を可能にします。

このガイドでは、FlaskベースのウェブアプリケーションをDockerコンテナ内で構築し、Apacheサーバーを通じて外部に公開する一連のプロセスをステップバイステップで説明します。この方法を用いることで、開発からデプロイメントに至るプロセスがスムーズになり、アプリケーションの移植性と拡張性が大幅に向上します。

それでは、実際の構築手順に入る前に、必要なコンポーネントとその役割について簡単に説明しましょう。


こちらの記事もおすすめ

GitLabのセットアップ入門: Docker Composeを使用した簡単なガイド
はじめにDocker Composeを使用してGitLabをセットアップするための初心者向けのガイドです。このプロセスを通じて、ソースコードのバージョン管理とコラボレーションツールであるGitLabを簡単に導入できます。こちらの記事もおすす...
GitHub Actionsを活用したAWS(EC2)自動デプロイ
はじめにこの記事では、Ubuntu 22.04.3 LTS環境でGitHubリポジトリへのSSH接続の設定と、GitHub Actionsを使用したEC2サーバー上のプロジェクトの自動デプロイについて解説します。このプロセスは、開発者が継続...

Flaskアプリケーションの準備

まず、基本的なFlaskアプリケーションを作成します。

Dockerfileの作成 :

Flaskアプリケーション用のDockerfileを作成します。このファイルはFlaskアプリケーションの依存関係をインストールし、アプリケーションを実行するために必要な指示を含んでいます。


FROM python:3.8
WORKDIR /usr/src/app
COPY requirements.txt ./
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
EXPOSE 5000
CMD ["flask", "run"]

Flaskアプリケーションの作成 (app.py):

一般的なFlaskアプリケーションを作成します。この例では、ルートURLにアクセスした際に「Hello, World!」と表示する単純なアプリケーションです。


from flask import Flask

app = Flask(__name__)

@app.route('/')
def hello_world():
    return 'Hello, World!'

if __name__ == '__main__':
    app.run(host='0.0.0.0', debug=True)

Apacheサーバーの設定

次に、Apacheサーバーを設定してFlaskアプリケーションにリクエストを転送します。

Apacheの設定ファイル (httpd.conf):

Apacheの設定ファイルには、プロキシモジュールのロード指示とVirtualHostの設定が含まれています。これにより、ApacheはFlaskアプリケーションにリクエストを転送します。

追加するコード


# --------------------------------------------------------------
# プロキシモジュールのロード
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so

# VirtualHost設定
<VirtualHost *:80>
    ProxyRequests Off
    ProxyPass / http://flask-app:5000/
    ProxyPassReverse / http://flask-app:5000/
</VirtualHost>

全体コード


#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log" 
# will be interpreted as '/logs/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/usr/local/apache2"

#
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
#
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
#
# Mutex default:logs

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule mpm_event_module modules/mod_mpm_event.so
#LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
#LoadModule mpm_worker_module modules/mod_mpm_worker.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authnz_fcgi_module modules/mod_authnz_fcgi.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule isapi_module modules/mod_isapi.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
#LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule socache_redis_module modules/mod_socache_redis.so
#LoadModule watchdog_module modules/mod_watchdog.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule bucketeer_module modules/mod_bucketeer.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
#LoadModule example_hooks_module modules/mod_example_hooks.so
#LoadModule case_filter_module modules/mod_case_filter.so
#LoadModule case_filter_in_module modules/mod_case_filter_in.so
#LoadModule example_ipc_module modules/mod_example_ipc.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule data_module modules/mod_data.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
#LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule reflector_module modules/mod_reflector.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule deflate_module modules/mod_deflate.so
#LoadModule xml2enc_module modules/mod_xml2enc.so
#LoadModule proxy_html_module modules/mod_proxy_html.so
#LoadModule brotli_module modules/mod_brotli.so
LoadModule mime_module modules/mod_mime.so
#LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule logio_module modules/mod_logio.so
#LoadModule lua_module modules/mod_lua.so
LoadModule env_module modules/mod_env.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_uwsgi_module modules/mod_proxy_uwsgi.so
#LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
#LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule proxy_hcheck_module modules/mod_proxy_hcheck.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_crypto_module modules/mod_session_crypto.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
#LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule optional_hook_export_module modules/mod_optional_hook_export.so
#LoadModule optional_hook_import_module modules/mod_optional_hook_import.so
#LoadModule optional_fn_import_module modules/mod_optional_fn_import.so
#LoadModule optional_fn_export_module modules/mod_optional_fn_export.so
#LoadModule dialup_module modules/mod_dialup.so
#LoadModule http2_module modules/mod_http2.so
#LoadModule proxy_http2_module modules/mod_proxy_http2.so
#LoadModule md_module modules/mod_md.so
#LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
#LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
#LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
#LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule heartbeat_module modules/mod_heartbeat.so
#LoadModule heartmonitor_module modules/mod_heartmonitor.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule info_module modules/mod_info.so
#LoadModule suexec_module modules/mod_suexec.so
<IfModule !mpm_prefork_module>
        #LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
        #LoadModule cgi_module modules/mod_cgi.so
</IfModule>
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
#LoadModule imagemap_module modules/mod_imagemap.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
#LoadModule rewrite_module modules/mod_rewrite.so

<IfModule unixd_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User www-data
Group www-data

</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80
ServerName 35.75.226.69

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other 
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/usr/local/apache2/htdocs"
<Directory "/usr/local/apache2/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   AllowOverride FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<Files ".ht*">
    Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /proc/self/fd/2

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog /proc/self/fd/1 common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/usr/local/apache2/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock cgisock
</IfModule>

#
# "/usr/local/apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/usr/local/apache2/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule headers_module>
    #
    # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied
    # backend servers which have lingering "httpoxy" defects.
    # 'Proxy' request header is undefined by the IETF, not listed by IANA
    #
    RequestHeader unset Proxy early
</IfModule>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
#EnableSendfile on

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf
</IfModule>

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

# --------------------------------------------------------------
# プロキシモジュールのロード
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so

# VirtualHost設定
<VirtualHost *:80>
    ProxyRequests Off
    ProxyPass / http://flask-app:5000/
    ProxyPassReverse / http://flask-app:5000/
</VirtualHost>

Docker Composeの使用

FlaskアプリケーションとApacheサーバーを管理するために、docker-compose.yml ファイルを使用します。

  1. ファイルの作成 :
    このファイルは、FlaskアプリケーションとApacheサーバーの両方を含むDockerサービスの構成を定義します。ここで、Flaskアプリケーションはビルドされ、Apacheサーバーは事前に構築された httpd イメージを使用します。

version: '3'

services:
  flask-app:
    build:
      context: ./flask
      dockerfile: Dockerfile
    ports:
      - "5000:5000"
    volumes:
      - ./flask:/usr/src/app
    environment:
      - FLASK_RUN_HOST=0.0.0.0
      - FLASK_APP=app.py

  apache:
    image: httpd
    stdin_open: true
    tty: true
    privileged: true
    ports:
      - "80:80"
    depends_on:
      - flask-app
    volumes:
      - ./apache/my-httpd.conf:/usr/local/apache2/conf/extra/httpd-vhosts.conf
      - ./apache/httpd.conf:/usr/local/apache2/conf/httpd.conf

サービスの起動 :

docker-compose up --build コマンドを使用して、FlaskアプリケーションとApacheサーバーのコンテナを起動します。ビルドプロセスの後、コンテナは起動し、ログが表示されます。


ubuntu@ip-172-31-45-101:~/prj/apfla$ sudo docker compose up --build
[+] Building 0.8s (10/10) FINISHED                                                                                                                                                                                                                       docker:default
 => [flask-app internal] load build definition from Dockerfile                                                                                                                                                                                                     0.0s
 => => transferring dockerfile: 193B                                                                                                                                                                                                                               0.0s
 => [flask-app internal] load .dockerignore                                                                                                                                                                                                                        0.0s
 => => transferring context: 2B                                                                                                                                                                                                                                    0.0s
 => [flask-app internal] load metadata for docker.io/library/python:3.8                                                                                                                                                                                            0.6s
 => [flask-app 1/5] FROM docker.io/library/python:3.8@sha256:7264a50439679c2868a99f71a5c9b9831cc082b1d3f05c8643788e1d7914afeb                                                                                                                                      0.0s
 => [flask-app internal] load build context                                                                                                                                                                                                                        0.0s
 => => transferring context: 564B                                                                                                                                                                                                                                  0.0s
 => CACHED [flask-app 2/5] WORKDIR /usr/src/app                                                                                                                                                                                                                    0.0s
 => CACHED [flask-app 3/5] COPY requirements.txt ./                                                                                                                                                                                                                0.0s
 => CACHED [flask-app 4/5] RUN pip install --no-cache-dir -r requirements.txt                                                                                                                                                                                      0.0s
 => [flask-app 5/5] COPY . .                                                                                                                                                                                                                                       0.0s
 => [flask-app] exporting to image                                                                                                                                                                                                                                 0.0s
 => => exporting layers                                                                                                                                                                                                                                            0.0s
 => => writing image sha256:b92469333071e917de3b900a182f791747de44fdabeb2f175e21d3e361d8fbe0                                                                                                                                                                       0.0s
 => => naming to docker.io/library/apfla-flask-app                                                                                                                                                                                                                 0.0s
[+] Running 2/2
 ✔ Container apfla-flask-app-1  Recreated                                                                                                                                                                                                                          0.1s 
 ✔ Container apfla-apache-1     Recreated                                                                                                                                                                                                                          0.1s 
Attaching to apfla-apache-1, apfla-flask-app-1
apfla-apache-1     | [Wed Dec 06 05:05:40.977274 2023] [mpm_event:notice] [pid 1:tid 140240498431872] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations
apfla-apache-1     | [Wed Dec 06 05:05:40.978312 2023] [core:notice] [pid 1:tid 140240498431872] AH00094: Command line: 'httpd -D FOREGROUND'
apfla-flask-app-1  |  * Serving Flask app 'app.py'
apfla-flask-app-1  |  * Debug mode: off
apfla-flask-app-1  | WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
apfla-flask-app-1  |  * Running on all addresses (0.0.0.0)
apfla-flask-app-1  |  * Running on http://127.0.0.1:5000
apfla-flask-app-1  |  * Running on http://172.18.0.2:5000
apfla-flask-app-1  | Press CTRL+C to quit
apfla-flask-app-1  | 172.18.0.1 - - [06/Dec/2023 05:05:52] "GET / HTTP/1.1" 200 -
apfla-apache-1     | 35.75.226.69 - - [06/Dec/2023:05:06:00 +0000] "GET / HTTP/1.1" 200 13
apfla-flask-app-1  | 172.18.0.3 - - [06/Dec/2023 05:06:00] "GET / HTTP/1.1" 200 -
apfla-apache-1     | 111.169.20.69 - - [06/Dec/2023:05:06:04 +0000] "GET / HTTP/1.1" 200 13
apfla-flask-app-1  | 172.18.0.3 - - [06/Dec/2023 05:06:04] "GET / HTTP/1.1" 200 -
apfla-apache-1     | 111.169.20.69 - - [06/Dec/2023:05:06:56 +0000] "-" 408 -
apfla-flask-app-1  | 172.18.0.3 - - [06/Dec/2023 05:15:37] "GET /v3/time HTTP/1.1" 404 -
apfla-apache-1     | 104.192.0.61 - - [06/Dec/2023:05:15:37 +0000] "GET /v3/time HTTP/1.1"

確認とテスト

最後に、設定が正しく機能していることを確認します。

Flaskアプリケーションのテスト :

Flaskアプリケーションは内部ポート5000で実行され、http://127.0.0.1:5000 または http://172.18.0.2:5000 でアクセスできます。


ubuntu@ip-172-31-45-101:~/prj/apfla$ curl http://localhost:5000/
Hello, World!

Apacheサーバー経由のテスト :

Apacheサーバーはポート80で実行され、ブラウザや curl コマンドを使用して http://localhost にアクセスすることでテストできます。


ubuntu@ip-172-31-45-101:~/prj/apfla$ curl http://localhost/
Hello, World!

これらの手順により、FlaskアプリケーションとApacheサーバーを含むDocker環境の基本的な構築とテストが完了します。この設定は開発環境に適しており、本番環境ではさらなるセキュリティ設定や最適化が必要になる可能性があります。

リポジトリ

GitHub - Sunwood-ai-labs/AWS-Docker-Apache_and_Flask
Contribute to Sunwood-ai-labs/AWS-Docker-Apache_and_Flask development by creating an account on GitHub.

参考URL

【備忘録】EC2 ubuntu内でDockerのhttpd(Apache)コンテナを起動してアクセスしても、403 Forbiddenとなる問題 - Qiita
現象EC2内で、ドキュメント通りにubuntu内にDocker Engineの立ち上げ。/home/ubuntuでhttpdのDockerコンテナをドキュメント通りに起動$ docker ru…
docker コンテナにログインした時の、デフォルトユーザを設定する。(docker-compose.yml)
docker コンテナにログインする時、特にユーザを指定しない場合は root ユーザでのログインになる事があるかと思います。 ですが、docker-compose.yml にて、コンテナにログインした時のデフォルトユーザを設定可能です。
DockerでFlask+Apache環境を作成する
Docker Composeを利用してFlask+Apacheの環境を作成したので、その方法をまとめておく。 環境 Docker Desktop(Windows10 Pro)。 PS > docker --version Docker version 20.10.7, ...
Docker + Python + FlaskでAPIサーバーを構築してみる | UnaBlog
Apache + Flask 環境の Dcokerfile を作成する - Qiita
この文章の前提Apache、Flask、Dockerが何かということの説明は割愛するDockerはホストマシンにインストール済みのものとして記載する目的Apache+Flask環境を他のマシ…
Docker + Flask + Apache – メモv3
docker-compose を用いて Apache・PHP・MySQL の開発環境を構築してみた - Qiita
はじめにdocker-compose を用いて Apache・PHP・MySQL の開発環境を構築してみた備忘録になります。構成図GitHub にもあげました。ご参考まで。できたこと以下を…
Docker入門~Apacheコンテナを起動しよう
 前回はDockerの基本的な仕組みと基礎知識について説明しました。今回は、実際にApacheが入ったhttpdイメージを使って、Webサーバーを立てていきながら、Dockerの基本を習得しましょう。
【中級者向け】「Docker compose」でサクッと複数のコンテナを一元管理する - DENET 技術ブログ
Docker Composeで3層ウェブアーキテクチャを構成する | NHN テコラス Tech Blog | AWS、Google Cloudなどのインフラ技術ブログ
この記事では、Docker Composeで3層ウェブアプリケーションを作成する手順を説明しました。Dockerのコマンドはたくさんあってややこしいですが、この記事で実際的な使い方とともに説明したことが少しでも役に立てば幸いです。
DockerとApacheを使ってWebサーバーを構築しよう - Avinton Japan
Amazon EC2インスタンスにDockerとApacheをインストールし、Webサーバーを構築していきます。Amazon EC2インスタンスにDockerをインストールし、Dockerでこしらえたコンテナの中にApacheを入れてWebサーバーを動かします!

コメント

タイトルとURLをコピーしました