如何使用 Elastic Beanstalk 创建 "tmp" 目录?
How can I create a "tmp" directory with Elastic Beanstalk?
我正在使用 Node.js 并且需要将文件保存到我的应用程序中的 tmp 目录。问题是 Elastic Beanstalk 没有将应用程序目录设置为可由应用程序写入。因此,当我尝试创建临时目录时出现此错误
fs.js:653
return binding.mkdir(pathModule._makeLong(path),
^
Error: EACCES, permission denied '/var/app/tmp/'
at Object.fs.mkdirSync (fs.js:653:18)
at Promise.<anonymous> (/var/app/current/routes/auth.js:116:18)
at Promise.<anonymous> (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
at Promise.emit (events.js:95:17)
at Promise.emit (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
at Promise.fulfill (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
at /var/app/current/node_modules/mongoose/lib/query.js:1394:13
at model.Document.init (/var/app/current/node_modules/mongoose/lib/document.js:250:11)
at completeOne (/var/app/current/node_modules/mongoose/lib/query.js:1392:10)
at Object.cb (/var/app/current/node_modules/mongoose/lib/query.js:1151:11)
我已经尝试了很多东西,例如 .ebextensions/scripts/app-setup.sh 中的 app-setup.sh 脚本,看起来像这样
#!/bin/bash
# Check if this is the very first time that this script is running
if ([ ! -f /root/.not-a-new-instance.txt ]) then
newEC2Instance=true
fi
# Get the directory of 'this' script
dirCurScript=$(dirname "${BASH_SOURCE[0]}")
# Fix the line endings of all files
find $dirCurScript/../../ -type f | xargs dos2unix -q -k
# Get the app configuration environment variables
source $dirCurScript/../../copy-to-slash/root/.elastic-beanstalk-app
export ELASTICBEANSTALK_APP_DIR="/$ELASTICBEANSTALK_APP_NAME"
appName="$ELASTICBEANSTALK_APP_NAME"
dirApp="$ELASTICBEANSTALK_APP_DIR"
dirAppExt="$ELASTICBEANSTALK_APP_DIR/.ebextensions"
dirAppTmp="$ELASTICBEANSTALK_APP_DIR/tmp"
dirAppData="$dirAppExt/data"
dirAppScript="$dirAppExt/scripts"
# Create tmp directory
mkdir -p $dirApp/tmp
# Set permissions
chmod 777 $dirApp
chmod 777 $dirApp/tmp
# Ensuring all the required environment settings after all the above setup
if ([ -f ~/.bash_profile ]) then
source ~/.bash_profile
fi
# If new instance, now it is not new anymore
if ([ $newEC2Instance ]) then
echo -n "" > /root/.not-a-new-instance.txt
fi
# Print the finish time of this script
echo $(date)
# Always successful exit so that beanstalk does not stop creating the environment
exit 0
以及在 .ebextensions 中创建一个名为 02_env.config 的文件,如下所示
# .ebextensions/99datadog.config
container_commands:
01mkdir:
command: "mkdir /var/app/tmp"
02chmod:
command: "chmod 777 /var/app/tmp"
似乎都不起作用。如何在我的应用程序中创建一个可写的 tmp 目录?
我最近遇到了与 .NET 应用程序相同的问题,该应用程序失败是因为它无法写入目录,即使在我设置了权限之后也是如此。
我发现在整个 .ebextensions 过程完成后,最后一步是 Web 容器权限更新,最终覆盖了我的 ebextensions 权限更改。
为了解决这个问题,我将目录移到了 Web 容器之外,并更新了应用程序以改为在其中写入。
对于你的情况,我建议 /tmp
随着较新的(当前的?)Amazon Linux 2 elastic beanstalk 安装,设置 Post 部署挂钩是实现这一目标的方法。在 elastic beanstalk 将新部署的应用程序包移动到 /var/app 后,需要创建 tmp 文件夹并使其可写。它只是一个 shell 脚本,位于应用根目录下的以下位置:
.platform/hooks/postdeploy/10_create_tmp_and_make_writeable.sh
#!/bin/bash
mkdir /var/app/current/tmp
chmod 777 /var/app/current/tmp
我正在使用 Node.js 并且需要将文件保存到我的应用程序中的 tmp 目录。问题是 Elastic Beanstalk 没有将应用程序目录设置为可由应用程序写入。因此,当我尝试创建临时目录时出现此错误
fs.js:653
return binding.mkdir(pathModule._makeLong(path),
^
Error: EACCES, permission denied '/var/app/tmp/'
at Object.fs.mkdirSync (fs.js:653:18)
at Promise.<anonymous> (/var/app/current/routes/auth.js:116:18)
at Promise.<anonymous> (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
at Promise.emit (events.js:95:17)
at Promise.emit (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
at Promise.fulfill (/var/app/current/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
at /var/app/current/node_modules/mongoose/lib/query.js:1394:13
at model.Document.init (/var/app/current/node_modules/mongoose/lib/document.js:250:11)
at completeOne (/var/app/current/node_modules/mongoose/lib/query.js:1392:10)
at Object.cb (/var/app/current/node_modules/mongoose/lib/query.js:1151:11)
我已经尝试了很多东西,例如 .ebextensions/scripts/app-setup.sh 中的 app-setup.sh 脚本,看起来像这样
#!/bin/bash
# Check if this is the very first time that this script is running
if ([ ! -f /root/.not-a-new-instance.txt ]) then
newEC2Instance=true
fi
# Get the directory of 'this' script
dirCurScript=$(dirname "${BASH_SOURCE[0]}")
# Fix the line endings of all files
find $dirCurScript/../../ -type f | xargs dos2unix -q -k
# Get the app configuration environment variables
source $dirCurScript/../../copy-to-slash/root/.elastic-beanstalk-app
export ELASTICBEANSTALK_APP_DIR="/$ELASTICBEANSTALK_APP_NAME"
appName="$ELASTICBEANSTALK_APP_NAME"
dirApp="$ELASTICBEANSTALK_APP_DIR"
dirAppExt="$ELASTICBEANSTALK_APP_DIR/.ebextensions"
dirAppTmp="$ELASTICBEANSTALK_APP_DIR/tmp"
dirAppData="$dirAppExt/data"
dirAppScript="$dirAppExt/scripts"
# Create tmp directory
mkdir -p $dirApp/tmp
# Set permissions
chmod 777 $dirApp
chmod 777 $dirApp/tmp
# Ensuring all the required environment settings after all the above setup
if ([ -f ~/.bash_profile ]) then
source ~/.bash_profile
fi
# If new instance, now it is not new anymore
if ([ $newEC2Instance ]) then
echo -n "" > /root/.not-a-new-instance.txt
fi
# Print the finish time of this script
echo $(date)
# Always successful exit so that beanstalk does not stop creating the environment
exit 0
以及在 .ebextensions 中创建一个名为 02_env.config 的文件,如下所示
# .ebextensions/99datadog.config
container_commands:
01mkdir:
command: "mkdir /var/app/tmp"
02chmod:
command: "chmod 777 /var/app/tmp"
似乎都不起作用。如何在我的应用程序中创建一个可写的 tmp 目录?
我最近遇到了与 .NET 应用程序相同的问题,该应用程序失败是因为它无法写入目录,即使在我设置了权限之后也是如此。
我发现在整个 .ebextensions 过程完成后,最后一步是 Web 容器权限更新,最终覆盖了我的 ebextensions 权限更改。
为了解决这个问题,我将目录移到了 Web 容器之外,并更新了应用程序以改为在其中写入。
对于你的情况,我建议 /tmp
随着较新的(当前的?)Amazon Linux 2 elastic beanstalk 安装,设置 Post 部署挂钩是实现这一目标的方法。在 elastic beanstalk 将新部署的应用程序包移动到 /var/app 后,需要创建 tmp 文件夹并使其可写。它只是一个 shell 脚本,位于应用根目录下的以下位置:
.platform/hooks/postdeploy/10_create_tmp_and_make_writeable.sh
#!/bin/bash
mkdir /var/app/current/tmp
chmod 777 /var/app/current/tmp