Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker fixes #1806

Merged
merged 5 commits into from Nov 2, 2019

Conversation

@Strubbl
Copy link
Contributor

Strubbl commented Nov 1, 2019

with this PR i could get pixelfed working via docker-compose.

With a valid .env file, the process to get pixelfed running is:

docker-compose up
docker-compose exec app php artisan migrate

Closes #1653

Strubbl added 2 commits Nov 1, 2019
In docker-compose, using a symlink from ./Dockerfile
to contrib/docker/Dockerfile.apache does not work. Therefore the symlink
is deleted and the docker-compose.yml is instructed to use the file
Dockerfile.apache in contrib by default.
This commit changes the default auth plugin of mysql to
mysql_native_password, because otherwise the laravel app couldn't
connect to the mysql database. The following error was thrown:

`SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client`
Strubbl added 2 commits Nov 1, 2019
This commit installs mysqldump via the package mariadb-client to make
use of `php artisan backup:run`. Without that package the command fails
with the following error:

```
$ docker-compose exec app php artisan backup:run
Starting backup...
Dumping database pixelfed...
Backup failed because The dump process failed with exitcode 127 : Command not found : sh: 1: mysqldump: not found
```
@Strubbl Strubbl force-pushed the Strubbl:docker-fixes branch from c12c6aa to c62978e Nov 1, 2019
@dansup
dansup approved these changes Nov 2, 2019
@dansup dansup merged commit 1ff1d12 into pixelfed:staging Nov 2, 2019
@Shleeble

This comment has been minimized.

Copy link
Contributor

Shleeble commented on c864f4b Nov 3, 2019

Why?

@Shleeble

This comment has been minimized.

Copy link
Contributor Author

Strubbl replied Nov 3, 2019

I always saw that the app failed to connect to redis in the laravel.log.

If that is not necessary, maybe also providing the .env to redis is not necessary. See: c864f4b

This comment has been minimized.

Copy link
Contributor Author

Strubbl replied Nov 3, 2019

the message in the laravel.log seem to get in the log when shutting down the containers. I am filing a new PR where i revert that changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.