nw.js: Failed to read DnsConfig

On OS X I have an alert that’s triggered on every node-webkit project that I run (including the sample apps), where the terminal throws the following:

[38459:0409/121155:WARNING:dns_config_service_posix.cc(289)] Failed to read DnsConfig.

The apps seem to run normally despite the issue and while investigating the warning all I could find was the part of Chromium’s source code that contains this trigger, but nothing else.

My question is if that’s an actual error of node-webkit and how it could be solved.

<bountysource-plugin>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

About this issue

  • Original URL
  • State: open
  • Created 10 years ago
  • Comments: 21 (4 by maintainers)

Most upvoted comments

I still need help with this.

When bugs go unfixed for a long time, they fix themselves!

Nice. I have the same issue, but it was resolved by bot 😃

@Christywl the issue/warning related with Alpine docker image and Chromium in my case:

Sample Dockerfile:

FROM gradle:jdk8-alpine

USER root
RUN apk -U --no-cache --allow-untrusted add \
   zlib-dev \
   chromium \
   wait4ports \
   dbus \
   ttf-freefont \
   chromium-chromedriver \
   grep

After built you can run:

$ docker run -it imagename  /usr/bin/chromium-browser --disable-web-security --headless --disable-gpu --no-sandbox --dump-dom  https://www.chromestatus.com | head -n 1

@miry @sholladay In 0.13 and later versions we changed to an optimized architecture so more features can be supported, see http://nwjs.io/blog/whats-new-in-0.13/ and it’s good for keeping up with Chromium upstream – we released with new Chromium versions within 1 day after upstream release. The new version would fixed many issues reported here and we’re scrubbing them. We’ll see if this issue still reproduce.

Backdoor to Chromium? This happens when I’m offline.