How volume user session in php-fpm container?

Question

My site based on code inside docker container with docker file like:

FROM php:7.1-fpm

RUN apt-get update && apt-get install -y libmcrypt-dev \
    mysql-client libmagickwand-dev --no-install-recommends \
    && pecl install imagick \
    && docker-php-ext-enable imagick \
    && docker-php-ext-install mcrypt pdo_mysql opcache gd

#ADD php.conf/opcache.ini    /etc/php/7.1/mods-available/opcache.ini
ADD build/prod/php.conf/www.conf       /usr/local/etc/php-fpm.d/
ADD build/prod/php.conf/php.ini        /usr/local/etc/php/

COPY .  /app

WORKDIR /app

RUN chmod 777 -R storage/
RUN php artisan cache:clear && php artisan key:generate
RUN nohup php artisan queue:work &

I build CI process just creating new app container with code and kill old. But after each such "recreation", users who were login are logged out. I'm sure that this is due to fact that old container contained PHP sessions, i wanted to add them to volume, but i cloud not found them. My php.ini:

session.save_handler = files
session.use_cookies = 1
session.cookie_path = /

i use Laravel framework, my sessions.php config has:

'driver' => 'file',
'files' => storage_path('framework/sessions'),
'path' => '/',

volume to path framework/sessions not helped

You could use Redis to do this sort of things, because it doesn't matter if you have a volume or not...when you will "recreate" the container...obviously the running container will be restarted. You could use volume however, you will also need to do rolling upgrades :) — Sergiu, Oct 25 '17 at 19:53
Can you try setting session.save_path (if you're not able to identify the location) http://php.net/manual/en/session.configuration.php#ini.session.save-path to where you want, and then using a mounted volume to your specified path? — Jay Dorsey, Oct 26 '17 at 00:48

score 0 · Accepted Answer · answered Oct 26 '17 at 02:52

When you run php artisan key:generate, it generates new value for APP_KEY. You can see it's value in .env file (project root)

APP_KEY is used to encrypt and decrypt the session data (and other stuff), so when you generate key again, laravel can't access previous session data.

If you use docker volumes for session files, but APP_KEY changes, sessions files from storage/framework/sessions become useless

This is easy to test locally by logging into your local website, running the command php artisan key:generate, and refreshing the page. You will be logged out.

To solve your problem with sessions use the same APP_KEY every time when you create a container.

You could pass key as environment variable to docker run -e APP_KEY='<key-here>' ..., but you need to enable environment variables

Note: even if you use different session driver (redis, database, memcached, ...), key should stay the same.

A bit more info about the Laravel's Application Key - what it is and how it works?

Laravel installation documentation Application Key

More about the laravel sessions

How volume user session in php-fpm container?

1 Answers1