Question

代码：container.yml

version: '2'
settings:
conductor_base: centos:7
services:
ansible.play_container:
from: "play:8_jre_security"
roles:
- play_container
ports:
- "9000:9000"
user: play
command: ['app/xxx/docker-entrypoint.sh']
registries: {}

OS / ENVIRONMENT Details :

Ansible Container, version 0.9.2
Linux, 3.10.0-327.13.1.el7.x86_64, #1 SMP Mon Feb 29 13:22:02 EST 2016, x86_64
2.7.5 (default, May 3 2017, 07:55:04)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] /usr/bin/python

使用的命令：sudo ansible-container --debug build

Error Log: 
 Fatal: [ansible.play_container]: FAILED! => {
    "changed": false,
    "module_stderr": "/_usr/bin/python: relocation error: /_usr/lib64/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference\n",
    "module_stdout": "",
    "msg": "MODULE FAILURE",
    "rc": 0
}
        to retry, use: --limit @/tmp/tmpXAGeVC/playbook.retry
PLAY RECAP *********************************************************************
ansible.play_container     : ok=0    changed=0    unreachable=0    failed=1
2017-11-28T06:09:14.110001 Error applying role!           [container.core] caller_file=/_ansible/container/core.py caller_func=apply_role_to_container caller_line=699 engine=<container.docker.engine.Engine object at 0x7fbcfd43ce90> exit_code=2 playbook=[{'hosts': u'ansible.play_container', 'roles': ['play_container'], 'vars': {}}]

请检查并提供解决重定位错误的步骤

Answer 1

导体基础图像和目标容器基础图像需要从相同的发行版派生。我猜测play:8_jre_security是什么，它不是CentOS 7派生的图像。

在ansible容器构建期间未定义的GLIBC_PRIVATE面临的问题

1 个答案: