Question

我尝试了dashDB Local的30天试用版。我按照链接中描述的步骤操作： https://www.ibm.com/support/knowledgecenter/en/SS6NHC/com.ibm.swg.im.dashdb.doc/admin/linux_deploy.html

我没有创建节点配置文件，因为我的是SMP设置。
登录我的docker hub帐户并提取图片。

docker login -u xxx -p yyyyy

docker pull ibmdashdb / local：latest-linux

拉动需要5分钟左右。我等待图像下载完成。

执行以下命令。它成功完成了。

docker run -d -it --privileged = true --net = host --name = dashDB -v / mnt / clusterfs：/ mnt / bludata0 -v / mnt / clusterfs：/ mnt / blumeta0 ibmdashdb / local：最新Linux的
运行日志命令

docker logs --follow dashDB

这表明dashDB没有启动但退出时出现错误代码130

# docker ps -a
CONTAINER ID        IMAGE                          COMMAND             CREATED             STATUS                       PORTS               NAMES
0f008f8e413d        ibmdashdb/local:latest-linux   "/usr/sbin/init"    16 seconds ago      Exited (130) 1 seconds ago                       dashDB
#

logs命令显示：

2017-05-17T17:48:11.285582000Z Detected virtualization docker.
2017-05-17T17:48:11.286078000Z Detected architecture x86-64.
2017-05-17T17:48:11.286481000Z
2017-05-17T17:48:11.294224000Z Welcome to dashDB Local!
2017-05-17T17:48:11.294621000Z
2017-05-17T17:48:11.295022000Z Set hostname to <orion>.
2017-05-17T17:48:11.547189000Z Cannot add dependency job for unit systemd-tmpfiles-clean.timer, ignoring: Unit is masked.
2017-05-17T17:48:11.547619000Z [  OK  ] Reached target Timers.
<snip>
2017-05-17T17:48:13.361610000Z [  OK  ] Started The entrypoint script for initializing dashDB local.
2017-05-17T17:48:19.729980000Z [100209.207731] start_dashDB_local.sh[161]: /usr/lib/dashDB_local_common_functions.sh: line 1816: /tmp/etc_profile-LOCAL.cfg: No such file or directory
2017-05-17T17:48:20.236127000Z [100209.713223] start_dashDB_local.sh[161]: The dashDB Local container's environment is not set up yet.
2017-05-17T17:48:20.275248000Z [  OK  ] Stopped Create Volatile Files and Directories.
<snip>
2017-05-17T17:48:20.737471000Z Sending SIGTERM to remaining processes...
2017-05-17T17:48:20.840909000Z Sending SIGKILL to remaining processes...
2017-05-17T17:48:20.880537000Z Powering off.

所以看起来start_dashDB_local.sh在/usr/lib/dashDB_local_common_functions.sh第1816行失败？我导出了图像，这是dashDB_local_common_functions.sh

update_etc_profile()
{
    local runtime_env=$1
    local cfg_file

    # Check if /etc/profile/dashdb_env.sh is already updated
    grep -q BLUMETAHOME /etc/profile.d/dashdb_env.sh
    if [ $? -eq 0 ]; then
        return
    fi
    case "$runtime_env" in
        "AWS" | "V1.5" )   cfg_file="/tmp/etc_profile-V15_AWS.cfg"
        ;;
        "V2.0" )   cfg_file="/tmp/etc_profile-V20.cfg"
        ;;
        "LOCAL" )  # dashDB Local Case and also the default
            cfg_file="/tmp/etc_profile-LOCAL.cfg"
        ;;
        *)  logger_error "Invalid ${runtime_env} value"
            return
        ;;
    esac

我还在图片中看到了/tmp/etc_profile-LOCAL.cfg。我错过了这里的任何一步吗？我还创建了/ mnt / clusterfs / nodes文件......但它没有帮助。相同的docker run命令以相同的方式失败。请帮忙。

我正在使用x86_64 Fedora25。

# docker version
Client:
 Version:         1.12.6
 API version:     1.24
 Package version: docker-common-1.12.6-6.gitae7d637.fc25.x86_64
 Go version:      go1.7.4
 Git commit:      ae7d637/1.12.6
 Built:           Mon Jan 30 16:15:28 2017
 OS/Arch:         linux/amd64

Server:
 Version:         1.12.6
 API version:     1.24
 Package version: docker-common-1.12.6-6.gitae7d637.fc25.x86_64
 Go version:      go1.7.4
 Git commit:      ae7d637/1.12.6
 Built:           Mon Jan 30 16:15:28 2017
 OS/Arch:         linux/amd64
#

# cat /etc/fedora-release
Fedora release 25 (Twenty Five)
# uname -r
4.10.15-200.fc25.x86_64
#

Answer 1

感谢您引起我们的注意。我联系了我们的开发团队。这似乎发生了，因为在容器内部，tmpfs被挂载到/ tmp并清除所有脚本

我们已经看到了这个问题，并且转向最新版本的docker似乎已经解决了这个问题。您的docker版本命令显示它是旧版本。

因此，请安装最新的docker版本并重试dashdb Local的部署并在此处进行更新。

此致穆拉利

Fedora 25上的dashDB Local - 错误代码130

1 个答案: