Skip to content
This repository has been archived by the owner on Jan 25, 2019. It is now read-only.

ds build fails #5

Open
jcommelin opened this issue Aug 22, 2018 · 9 comments
Open

ds build fails #5

jcommelin opened this issue Aug 22, 2018 · 9 comments

Comments

@jcommelin
Copy link

I followed the instructions:

git clone https://github.com/docker-scripts/ds /opt/docker-scripts/ds
cd /opt/docker-scripts/ds/
make install
ds -h
ds pull wsproxy
ds init wsproxy @wsproxy
cd /var/ds/wsproxy/
pwd
vim settings.sh
ds build

but it fails with the following error:

Reading package lists...
Building dependency tree...
Reading state information...
Package systemd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'systemd' has no installation candidate
The command '/bin/sh -c apt update &&     apt upgrade --yes &&     apt install --yes systemd &&     systemctl set-default multi-user.target' returned a non-zero code: 100
@dashohoxha
Copy link
Member

Can you share (on pastebin or somewhere else) the log file (/var/ds/wsproxy/logs/wsproxy-......out)?

@jcommelin
Copy link
Author

Voila: https://pastebin.com/iPVRwCYd
Somehow it can't resolve the Ubuntu archives... my host definitely has internet access. Did I miss some step where I had to provide internet access to the ds container?

@dashohoxha
Copy link
Member

It says: Temporary failure resolving 'archive.ubuntu.com' Maybe you should try again.
As far as I know, there is no special configuration needed to allow docker containers access to the Internet.
Maybe there is something on your firewall that prevents this?
Can you share the output of iptables-save?

@jcommelin
Copy link
Author

Voila: https://pastebin.com/34DrCs7K
Maybe I overlooked something, but this seems standard to me.

@dashohoxha
Copy link
Member

Unfortunately I don't understand nft. I can only understand the output of iptables-save. So, I cannot say anything and cannot help you.

Anyway, whatever is the problem, it is a docker problem, not a docker-script problem, so most probably you can find some solution on the web without my help.

@jcommelin
Copy link
Author

Ok, thanks for your help so far. I'll dig into the docker issue.

@jcommelin
Copy link
Author

Ok, so ds build --network=host did the trick. My docker config is plain vanilla. Should I have added something in order to make ds build work?

@jcommelin
Copy link
Author

@dashohoxha Sorry for bugging you again. If ran ds create and ds config, and now I have a wsproxy container. However, again it does not have network connection. I also tried to add --network=host to these two commands, but it does not make a difference. Do you know what I should do?

@dashohoxha
Copy link
Member

Most probably there is something in the firewall that prevents it to connect to internet.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants