Dockerfile HOSTNAME 用于 docker build 的指令，如 docker run -h

本文介绍了Dockerfile HOSTNAME 用于 docker build 的指令，如 docker run -h的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我正在尝试在构建过程中在 docker 容器中设置主机名，因为某些软件安装使用发现的随机生成的主机名并将该主机名永久烘焙到配置中.

I am attempting to set the hostname inside a docker container during the build since certain software installs use the discovered randomly generated hostname and permanently bake that hostname into the configuration.

虽然可以通过 run -h 交互式运行时设置主机名，但通过 Dockerfile 构建时无法使用相同的功能.

While it is possible to set the hostname when you run interactively via run -h, the same functionality is not available using build via the Dockerfile.

解决此问题的唯一方法是使用 LD_PRELOAD hack，以便我可以将主机名设置为 localhost.LD_PRELOAD hack 有一些不想要的副作用，我无法解决这些副作用.使用docker run -it -h localhost"时，软件安装没有问题.

The only way to work around this is to use LD_PRELOAD hacks so that I can set the hostname to localhost. The LD_PRELOAD hacks have unwanted sideeffects that I am having trouble working around. The software install works without issue when using "docker run -it -h localhost ".

strace 报告安装程序调用 uname 确定主机名.

strace reports that the installer make a call to uname determine the hostname.

uname({sys="Linux", node="12b0c7c7eacb", ...}) = 0

有谁知道如何解决这个限制?

Does anyone know how it might be possible to work around this limitation?

更新 1

这不是问题 How to handle specific hostname like -h option in Dockerfile 的重复问题，因为这是专门讨论的动态生成该文件引起的/etc/hosts"问题.这很容易解决，因为它是一个可写文件.

This is not a duplicate of the question How to handle specific hostname like -h option in Dockerfile as that is talking specifically about "/etc/hosts" problems arising from that file being dynamically generated. This is easily worked around since it is a writable file.

这是关于尝试从系统调用(例如 uname 和 gethostname)解析主机名的软件安装.据我所知，这是无法解决的，因为无法在正在运行的 docker 容器中更改主机名.uname 系统调用可能引用/proc/sys/kernel/hostname，这是只读的，不能更改.通常可以运行 hostname 命令，但是该命令会生成一个错误，即即使您是 root，您也必须是 root.解决方法是使用 -h 标志，这在构建中不可用.

This is about software installs that attempt to resolve the hostname from system calls such as uname and gethostname. From what I can tell this cannot be worked around since the hostname cannot be changed within a running docker container. The uname system call likely references /proc/sys/kernel/hostname, this is read only and cannot be changed. Normally the hostname command could be run, but this command generates an error that you must be root even if you are root. The workaround for this is to use the -h flag, this is not available in builds.

更新 2

对于任何在这里寻找解决方法的人来说，这只需要在 docker 构建期间使用，如果您需要使用 docker run 自定义主机名，请使用 -h 标志.这是基于其他人的工作.

For anyone looking for a workaround here it is, this only needs to be used during the docker build, use the -h flag if you need to customize the hostname with docker run. This is based on someone else's work.

Dockerfile:

RUN gcc -o fakehostname.o -c -fPIC -Wall fakehostname.c
RUN gcc -o libfakehostname.so -shared -W1,export-dynamic fakehostname.o -ldl

RUN ..
     export LD_PRELOAD=/u01/app/oracle/libfakehostname.so;
     installer section
    ..

C 来源:

#define _GNU_SOURCE
#include <unistd.h>
#include <sys/syscall.h>
#include <sys/types.h>
#include <sys/utsname.h>

#include <stdio.h>
#include <string.h>

static int (*real_gethostname)(char *name, size_t len);

int uname(struct utsname *buf)
{
 int ret;

 ret = syscall(SYS_uname, buf);

 strcpy(buf->nodename, "localhost");

 return ret;
}

int gethostname(char *name, size_t len)
{
  const char *val;

  /* Override hostname */
  val = "localhost";
  if (val != NULL)
  {
    strncpy(name, val, len);
    return 0;
  }

  /* Call real gethostname() */
  return real_gethostname(name, len);
}

http://github.com/docker/docker/issues 根据 into_the_void，因为这个问题没有解决办法.

http://github.com/docker/docker/issues as per into_the_void as there is no solution to this problem.

的指令

Dockerfile HOSTNAME 用于 docker build 的指令，如 docker run -h

问题描述

推荐答案