Closed un-fuf-a-doo closed 3 years ago
un-fuf-a-doo
commented
3 years ago So what is going on? This issue is definitely with your image because I currently have 3 containers running successfully, pulled and run the same way. Only your 7dtd-server will not work.
Further error says...Unable to resolve hostname.
un-fuf-a-doo
commented
3 years ago Tried to build your image from your Dockerfile and it fails with unable to resolve domain names.
Sending build context to Docker daemon 3.584kB
Step 1/33 : FROM didstopia/base:nodejs-12-steamcmd-ubuntu-18.04
nodejs-12-steamcmd-ubuntu-18.04: Pulling from didstopia/base
a1125296b23d: Pull complete
3c742a4a0f38: Pull complete
4c5ea3b32996: Pull complete
1b4be91ead68: Pull complete
59e6af739438: Pull complete
abc79d0a6811: Pull complete
753f61eb0101: Pull complete
027291fdda82: Pull complete
71cccd022ace: Pull complete
95b02d81fd99: Pull complete
aaa0159d3c8f: Pull complete
600d15ae64c2: Pull complete
b3ec240f27f2: Pull complete
774b17ec1eac: Pull complete
68f48fb2738f: Pull complete
48657a7cf8ce: Pull complete
Digest: sha256:fd8e5f55b772e3129233a0df615fe65eea1d510ff2594f786602132be5468bab
Status: Downloaded newer image for didstopia/base:nodejs-12-steamcmd-ubuntu-18.04
---> 865b7e671b91
Step 2/33 : LABEL maintainer="Didstopia <support@didstopia.com>"
---> Running in c9fa23978dab
Removing intermediate container c9fa23978dab
---> 637fe8606961
Step 3/33 : ARG DEBIAN_FRONTEND=noninteractive
---> Running in 0d55b160ec8e
Removing intermediate container 0d55b160ec8e
---> bb4a2fd1dec1
Step 4/33 : USER root
---> Running in 84082fd79964
Removing intermediate container 84082fd79964
---> 0a8f1e917193
Step 5/33 : RUN apt-get update && apt-get install -y --no-install-recommends xvfb telnet vim net-tools expect && rm -rf /var/lib/apt/lists/*
---> Running in d82937a6cbd6
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 https://deb.nodesource.com/node_12.x bionic InRelease
Temporary failure resolving 'deb.nodesource.com'
Err:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch https://deb.nodesource.com/node_12.x/dists/bionic/InRelease Temporary failure resolving 'deb.nodesource.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package xvfb
E: Unable to locate package telnet
E: Unable to locate package vim
E: Unable to locate package net-tools
E: Unable to locate package expect
The command '/bin/sh -c apt-get update && apt-get install -y --no-install-recommends xvfb telnet vim net-tools expect && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
Happy New Year...
I know this is probably something minor, but on a fresh pull and container creation, steamcmd is not able to connect to the servers to download the game data.
I'm pretty sure my network works just fine since I was able to download the image. I have other containers running just fine as well. By the way, thanks for doing this, it really saves a lot of time.