Dear @bobbyiliev,

i resolved the “Auth.login view not found ” by simply clearing cache, config etc, using commands php artisan clear:cache, view:clear etc.
This trick is the first thing our University Professor taught us when developing with Laravel, and still the first thing I forgot to do. Damn :)
The problem was the dirty cache which contained data from my host system ,which was inherited by the virtualization of the php image.

about the dependency problem: I resolved it by running further commands into the container. I specified different versions of the dependency which should have worked for this particular php image, and then “composer install” finally worked, and conflicts was resolved.

But this last issue was the lesser in importance.
The first one I wrote about was the one that really blocked me.

Now the app works fine. This tutorial was absolutely perfect, nothing to say.

I share with you the Dockerfile, as you asked, nonetheless.

FROM php:7.4-fpm
ARG user
ARG uid
RUN apt-get update && apt-get install -y \
git \
curl \
libpng-dev \
libonig-dev \
libxml2-dev \
zip \
unzip
RUN apt-get clean && rm -rf /var/lib/apt/lists/*
RUN docker-php-ext-install pdo_mysql mbstring exif pcntl bcmath gd
COPY –from=composer:latest /usr/bin/composer /usr/bin/composer
RUN useradd -G www-data,root -u $uid -d /home/$user $user
RUN mkdir -p /home/$user/.composer && \
chown -R $user:$user /home/$user
WORKDIR /var/www
USER $user

PS; I thank you so much for your time, your availability, and your kindness.

My best regards,

Lorenzo Battelli

Dear @bobbyiliev,

I’ve been trying to resolve another problem for 2 weeks. By taking this tutorial about “containerizing our Laravel application with docker-compose” as start point, I tried to deploy my new docker image (created with “docker-compose build app”, as we seen in the guide) to my DockerHub repository. In order to do this, I tried to run

docker image push <repoName>:latest

then it was successfully push to my repo.
But here’s the problem, let’s assume I’m someone else, (a co-worker for example), and I want to pull this application that has been previously push to the repo with docker image push …, after the pulling I get an empty image, in particular if I run

docker container run -it <pulled_Image_Name> bash

and visit /var/www/ I notice that this directory doesn’t contain my Laravel application file, but only an empty directory called “html”. So this image is useless for everyone who want to pull my application. Maybe is that something wrong in Pushing process?

Maybe is the dir /var/www empty because of some lack in the Dockerfile?

Plan B, I tried to run the pulled image by using
docker-compose up
but obviously it says “docker compose file not found”.

I really don’t understand how to deploy on DockerHub a multi-containerized Laravel application with docker-compose, in order to let other people pulling it and running it.

Thank you very much,

Lorenzo Battelli