Question

我在我的单一容器EB部署中使用亚马逊提供的新弹性文件系统。我无法弄清楚为什么挂载的EFS无法映射到容器中。

在/ efs-mount-point上的主机上成功执行了EFS安装。

提供给Dockerrun.aws.json是

{
  "AWSEBDockerrunVersion": "1"
  "Volumes": [
    {
      "HostDirectory": "/efs-mount-point",
      "ContainerDirectory": "/efs-mount-point"
    }
  ]
}

然后，一旦卷开始运行，就会在容器中创建该卷。但是它已映射hosts目录/ efs-mount-point，而不是实际的EFS挂载点。我无法弄清楚如何让Docker映射到安装在/ efs-mount-point而不是主机目录的EFS卷中。

NFS卷与Docker一起玩得好吗？

Answer 1

在主机EC2实例中安装EFS卷后，您需要restart docker。

以下是一个示例，commands: 01mkdir: command: "mkdir -p /efs-mount-point" 02mount: command: "mountpoint -q /efs-mount-point || mount -t nfs4 -o nfsvers=4.1 $(curl -s http://169.254.169.254/latest/meta-data/placement/availability-zone).fs-fa35c253.efs.us-west-2.amazonaws.com:/ /efs-mount-point" 03restart: command: "service docker restart"：

{{1}}

Answer 2

使用AWS Beanstalk进行EFS - Multicontainer Docker将正常运行。但是许多事情都会停止工作，因为你必须在安装EFS后重新启动docker。

实例命令

搜索你可能会发现你需要做＃14; docker restart＆＃34;安装EFS后。事情并非如此简单。当自动调节发生时和/或部署新版本的应用程序时，您将遇到麻烦。

下面是我用于将EFS安装到docker实例的脚本，其中需要执行以下步骤：

停止ECS经理。需要60秒。
停止Docker服务
杀死剩余的码头工作者
删除网络以前的绑定。请参阅问题https://github.com/docker/docker/issues/7856#issuecomment-239100381
装载EFS
启动泊坞窗服务。
启动ECS服务
等待120秒。使ECS达到正确的启动/ *状态。否则，例如00enact脚本将失败。请注意，此显示是必需的，很难找到任何文档。

这是我的剧本：

.ebextensions/commands.config：

commands:
  01stopdocker:
    command: "sudo stop ecs  > /dev/null 2>&1 || /bin/true && sudo service docker stop"
  02killallnetworkbindings:
    command: 'sudo killall docker  > /dev/null 2>&1 || /bin/true'
  03removenetworkinterface:
    command: "rm -f /var/lib/docker/network/files/local-kv.db"
    test: test -f /var/lib/docker/network/files/local-kv.db
  # Mount the EFS created in .ebextensions/media.config
  04mount:
    command: "/tmp/mount-efs.sh"
  # On new instances, delay needs to be added because of 00task enact script. It tests for start/ but it can be various states of start...
  # Basically, "start ecs" takes some time to run, and it runs async - so we sleep for some time.
  # So basically let the ECS manager take it's time to boot before going on to enact scritps and post deploy scripts.
  09restart:
    command: "service docker start && sudo start ecs && sleep 120s"

安装脚本和环境变量

.ebextensions/mount-config.config

# efs-mount.config
# Copy this file to the .ebextensions folder in the root of your app source folder
option_settings:
  aws:elasticbeanstalk:application:environment:
    EFS_REGION: '`{"Ref": "AWS::Region"}`'
    # Replace with the required mount directory
    EFS_MOUNT_DIR: '/efs_volume'
    # Use in conjunction with efs_volume.config or replace with EFS volume ID of an existing EFS volume
    EFS_VOLUME_ID: '`{"Ref" : "FileSystem"}`'

packages:
  yum:
    nfs-utils: []
files:
  "/tmp/mount-efs.sh":
      mode: "000755"
      content : |
        #!/bin/bash

        EFS_REGION=$(/opt/elasticbeanstalk/bin/get-config environment | jq -r '.EFS_REGION')
        EFS_MOUNT_DIR=$(/opt/elasticbeanstalk/bin/get-config environment | jq -r '.EFS_MOUNT_DIR')
        EFS_VOLUME_ID=$(/opt/elasticbeanstalk/bin/get-config environment | jq -r '.EFS_VOLUME_ID')

        echo "Mounting EFS filesystem ${EFS_DNS_NAME} to directory ${EFS_MOUNT_DIR} ..."

        echo 'Stopping NFS ID Mapper...'
        service rpcidmapd status &> /dev/null
        if [ $? -ne 0 ] ; then
            echo 'rpc.idmapd is already stopped!'
        else
            service rpcidmapd stop
            if [ $? -ne 0 ] ; then
                echo 'ERROR: Failed to stop NFS ID Mapper!'
                exit 1
            fi
        fi

        echo 'Checking if EFS mount directory exists...'
        if [ ! -d ${EFS_MOUNT_DIR} ]; then
            echo "Creating directory ${EFS_MOUNT_DIR} ..."
            mkdir -p ${EFS_MOUNT_DIR}
            if [ $? -ne 0 ]; then
                echo 'ERROR: Directory creation failed!'
                exit 1
            fi
            chmod 777 ${EFS_MOUNT_DIR}
            if [ $? -ne 0 ]; then
                echo 'ERROR: Permission update failed!'
                exit 1
            fi
        else
            echo "Directory ${EFS_MOUNT_DIR} already exists!"
        fi

        mountpoint -q ${EFS_MOUNT_DIR}
        if [ $? -ne 0 ]; then
            AZ=$(curl -s http://169.254.169.254/latest/meta-data/placement/availability-zone)
            echo "mount -t nfs4 -o nfsvers=4.1 ${AZ}.${EFS_VOLUME_ID}.efs.${EFS_REGION}.amazonaws.com:/ ${EFS_MOUNT_DIR}"
            mount -t nfs4 -o nfsvers=4.1 ${AZ}.${EFS_VOLUME_ID}.efs.${EFS_REGION}.amazonaws.com:/ ${EFS_MOUNT_DIR}
            if [ $? -ne 0 ] ; then
                echo 'ERROR: Mount command failed!'
                exit 1
            fi
        else
            echo "Directory ${EFS_MOUNT_DIR} is already a valid mountpoint!"
        fi

        echo 'EFS mount complete.'

资源和配置

您必须更改以下的option_settings。要查找您必须在下面的option_settings下定义的VPC和子网，请查看AWS Web控制台 - ＆gt;在VPC中，您必须找到默认VPC ID和3个默认子网ID。如果您的beanstalk使用自定义VPC，则必须使用这些设置。

.ebextensions/efs-volume.config：

# efs-volume.config
# Copy this file to the .ebextensions folder in the root of your app source folder
option_settings:
  aws:elasticbeanstalk:customoption: 
    EFSVolumeName: "EB-EFS-Volume"
    VPCId: "vpc-xxxxxxxx"
    SubnetUSWest2a: "subnet-xxxxxxxx"
    SubnetUSWest2b: "subnet-xxxxxxxx"
    SubnetUSWest2c: "subnet-xxxxxxxx"

Resources:
  FileSystem:
    Type: AWS::EFS::FileSystem
    Properties:
      FileSystemTags:
      - Key: Name
        Value:
          Fn::GetOptionSetting: {OptionName: EFSVolumeName, DefaultValue: "EB_EFS_Volume"}
  MountTargetSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupDescription: Security group for mount target
      SecurityGroupIngress:
      - FromPort: '2049'
        IpProtocol: tcp
        SourceSecurityGroupId:
          Fn::GetAtt: [AWSEBSecurityGroup, GroupId]
        ToPort: '2049'
      VpcId:
        Fn::GetOptionSetting: {OptionName: VPCId}
  MountTargetUSWest2a:
    Type: AWS::EFS::MountTarget
    Properties:
      FileSystemId: {Ref: FileSystem}
      SecurityGroups:
      - {Ref: MountTargetSecurityGroup}
      SubnetId:
        Fn::GetOptionSetting: {OptionName: SubnetUSWest2a}
  MountTargetUSWest2b:
    Type: AWS::EFS::MountTarget
    Properties:
      FileSystemId: {Ref: FileSystem}
      SecurityGroups:
      - {Ref: MountTargetSecurityGroup}
      SubnetId:
        Fn::GetOptionSetting: {OptionName: SubnetUSWest2b}
  MountTargetUSWest2c:
    Type: AWS::EFS::MountTarget
    Properties:
      FileSystemId: {Ref: FileSystem}
      SecurityGroups:
      - {Ref: MountTargetSecurityGroup}
      SubnetId:
        Fn::GetOptionSetting: {OptionName: SubnetUSWest2c}

资源：

有关装配问题：https://forums.aws.amazon.com/message.jspa?messageID=730288#730555
对于网络端口映射问题：https://github.com/docker/docker/issues/7856
对于EFS安装脚本：https://forums.aws.amazon.com/thread.jspa?messageID=733181

Answer 3

AWS有关于在弹性beanstalk上自动创建和安装EFS的说明。他们可以找到here

这些说明链接到两个要自定义的配置文件，并放置在部署包的 .ebextensions 文件夹中。

storage-efs-createfilesystem.config
storage-efs-mountfilesystem.config

需要进一步修改 storage-efs-mountfilesystem.config 文件以使用Docker容器。添加以下命令：

02_restart:
  command: "service docker restart"

对于多容器环境，Elastic Container Service也必须重新启动（在上面的docker重启时它被杀死了）：

03_start_eb:
  command: |
      start ecs
      start eb-docker-events
      sleep 120
  test: sh -c "[ -f /etc/init/ecs.conf ]"

所以 storage-efs-mountfilesystem.config 的完整命令部分是：

commands:
  01_mount:
    command: "/tmp/mount-efs.sh"
  02_restart:
    command: "service docker restart"
  03_start_eb:
    command: |
        start ecs
        start eb-docker-events
        sleep 120
    test: sh -c "[ -f /etc/init/ecs.conf ]"

这不起作用的原因＆＃34;开箱即用＆＃34;是因为在运行.ebextensions中的命令之前，EC2实例启动了docker守护程序。启动顺序是：

启动docker守护程序
在多容器泊坞窗环境中启动弹性容器服务代理
在.ebextensions
运行容器应用

在第一步，docker守护程序提供给容器的文件系统视图是固定的。因此，在步骤3中进行的主机文件系统的更改不会反映在容器的视图中。

一个奇怪的影响是容器在文件系统挂载到主机之前看到一个挂载点。主机看到挂载的文件系统。因此，容器写入的文件将写入安装目录下的主机目录，而不是挂载的文件系统。卸载EC2主机上的文件系统将公开写入安装目录的容器文件。

将AWS EFS与Docker配合使用

3 个答案:

实例命令

安装脚本和环境变量

资源和配置