执行artisan backup:run时未找到Laradock mysqldump(Spatie Laravel备份) [英] Laradock mysqldump not found when executing artisan backup:run (Spatie Laravel Backup)
问题描述
我已经在Laradock上部署了Laravel应用程序.
I have deployed a Laravel application with Laradock.
我想指出数据库连接正常(用户可以注册，登录等).
为了备份该应用程序，我安装了 Spatie的Laravel Backup软件包.
In order to back up the application, I have installed the Spatie's Laravel Backup package.
我相应地设置了所有配置变量，如下所示:
I set up all config variables accordingly as follows:
config/backup.php
<?php
return [
'backup' => [
/*
* The name of this application. You can use this name to monitor
* the backups.
*/
'name' => env('APP_NAME', 'laravel-backup'),
'source' => [
/*......*/
/*
* The names of the connections to the databases that should be backed up
* MySQL, PostgreSQL, SQLite and Mongo databases are supported.
*
* The content of the database dump may be customized for each connection
* by adding a 'dump' key to the connection settings in config/database.php.
* E.g.
* 'mysql' => [
* ...
* 'dump' => [
* 'excludeTables' => [
* 'table_to_exclude_from_backup',
* 'another_table_to_exclude'
* ]
* ],
* ],
*
* If you are using only InnoDB tables on a MySQL server, you can
* also supply the useSingleTransaction option to avoid table locking.
*
* E.g.
* 'mysql' => [
* ...
* 'dump' => [
* 'useSingleTransaction' => true,
* ],
* ],
*
* For a complete list of available customization options, see https://github.com/spatie/db-dumper
*/
'databases' => [
'mysql',
],
],
/*
* The database dump can be compressed to decrease diskspace usage.
*
* Out of the box Laravel-backup supplies
* Spatie\DbDumper\Compressors\GzipCompressor::class.
*
* You can also create custom compressor. More info on that here:
* https://github.com/spatie/db-dumper#using-compression
*
* If you do not want any compressor at all, set it to null.
*/
'database_dump_compressor' => null,
/*....*/
],
],
];
在Laravel Homestead中，备份工作正常.
In Laravel Homestead the backup works fine.
$ php artisan backup:run .
此软件包的文档，我们需要指定 mysqldump 二进制文件的路径，如下所示:
According to this package's docs, we need to specify the path to the mysqldump binaries as follows:
config/database.php
//config/database.php
'connections' => [
'mysql' => [
'driver' => 'mysql'
...,
'dump' => [
'dump_binary_path' => '/path/to/the/binary', // only the path, so without `mysqldump` or `pg_dump`
'use_single_transaction',
'timeout' => 60 * 5, // 5 minute timeout
'exclude_tables' => ['table1', 'table2'],
'add_extra_option' => '--optionname=optionvalue',
]
],
这是我默认在同一文件中得到的:
This is what I got by default in that same file:
'mysql' => [
'driver' => 'mysql',
'url' => env('DATABASE_URL'),
'host' => env('DB_HOST', '127.0.0.1'),
'port' => env('DB_PORT', '3306'),
'database' => env('DB_DATABASE', 'forge'),
'username' => env('DB_USERNAME', 'forge'),
'password' => env('DB_PASSWORD', ''),
'unix_socket' => env('DB_SOCKET', ''),
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
'prefix' => '',
'prefix_indexes' => true,
'strict' => true,
'engine' => null,
'options' => extension_loaded('pdo_mysql') ? array_filter([
PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
]) : [],
'dump'=>[
'dump_binary_path' => env('DB_DUMP_PATH'), // only the path, so without `mysqldump` or `pg_dump`
'use_single_transaction',
'timeout' => 60 * 5, // 5 minute timeout
//'exclude_tables' => ['table1', 'table2'],
//'add_extra_option' => '--optionname=optionvalue',
'add_extra_option' => '--host='.env('DB_HOST'),
]
],
在我的 .env 文件中:
DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DUMP_PATH='/usr/bin/'
如果我在MySQL容器内执行 mysqldump ，它将起作用:
If I execute the mysqldump inside the MySQL container, it does work:
Usage: mysqldump [OPTIONS] database [tables]
OR mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
OR mysqldump [OPTIONS] --all-databases [OPTIONS]
For more options, use mysqldump --help
但是，如果我在工作区容器中运行backup命令，
However, If I run the backup command inside the workspace container,
工匠备份:运行
我得到了错误:
备份失败，因为:转储过程失败，退出代码为127:找不到命令:sh:1:mysqldump:找不到
Backup failed because: The dump process failed with exitcode 127 : Command not found : sh: 1: mysqldump: not found
那我如何告诉Laradock mysqldump二进制路径在哪里?
Then how do I tell Laradock where the mysqldump binary path is located?
有解决方法吗?也许要建立一个新的容器来将 Workspace 与 MySQL 容器连接起来?
Is there a workaround? Maybe setting up a new container that connects the Workspace with the MySQL container?
还有其他方法吗?
在Adrien的帮助下解决就在 .env 文件中，我确实发现以下变量设置为false:
SOLVING with the help of Adrien
Right at the .env file, I indeed found that the following variable is set to false:
### WORKSPACE #############################################
####
# ...
WORKSPACE_INSTALL_MYSQL_CLIENT=false
# ...
所以我将其更改为true:
So i changed that to true:
### WORKSPACE #############################################
####
# ...
WORKSPACE_INSTALL_MYSQL_CLIENT=true
# ...
我保存并退出.
这也意味着我不必在 docker-compose.custom.yml 文件
This also means that I don't have to make any more changes in the docker-compose.custom.yml file
要应用该更改，我执行了(无需停止任何容器)
To apply that change, I executed (without having to stop any container)
$ docker-compose build workspace
$ docker-compose -f docker-compose.custom.yml up -d workspace
然后我进入了容器
$ docker exec -it my_workspace bash
一旦我在里面寻找mysqldump:
Once inside I looked for mysqldump:
# which mysqldump
/usr/bin/mysqldump
最后，我可以执行Spatie的Laravel Backup软件包:
Finally I could execute the Spatie's Laravel Backup package:
# artisan backup:run
Starting backup...
Dumping database xyz...
Determining files to backup...
Zipping x files and directories...
Created zip containing x files and directories. Size is x.x MB
Copying zip to disk named backMeUp...
Successfully copied zip to disk named backMeUp.
Backup completed!
那就成功了！
推荐答案
如此处所述，编辑laradock .env 文件并设置:
As mentioned here, edit laradock .env file and set:
WORKSPACE_INSTALL_MYSQL_CLIENT=true
然后运行:
docker-compose build workspace && docker-composer up -d workspace
这将更新您的工作区容器并重新启动它.
That will update your workspace container and restart it.
连接到您的容器:
docker-compose exec workspace bash
您应该有权访问 mysqldump :
root@82d8b3b3c0a0:/var/www# which mysqldump
/usr/bin/mysqldump
这篇关于执行artisan backup:run时未找到Laradock mysqldump(Spatie Laravel备份)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
