bug report #52
Comments
|
when running the 'docker-compose up -d' script I get the following error: |
|
Please list your OS and version. This sounds to me like you might not have rebooted when asked to do so? |
|
I am running Ubuntu 18 on a mac laptop. I did reboot at the prompt but
still get the error.
…On Thu, Jun 21, 2018 at 9:08 AM Eric Nemchik ***@***.***> wrote:
Please list your OS and version.
This sounds to me like you might not have rebooted when asked to do so?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQp46BqpXfaW-bOpWqzi87Keqpijuks5t-5rRgaJpZM4UyAU2>
.
|
|
Specifically Ubuntu 18.04 LTS
…On Thu, Jun 21, 2018 at 9:11 AM Mike McMichael ***@***.***> wrote:
I am running Ubuntu 18 on a mac laptop. I did reboot at the prompt but
still get the error.
On Thu, Jun 21, 2018 at 9:08 AM Eric Nemchik ***@***.***>
wrote:
> Please list your OS and version.
>
> This sounds to me like you might not have rebooted when asked to do so?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#52 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQCpQp46BqpXfaW-bOpWqzi87Keqpijuks5t-5rRgaJpZM4UyAU2>
> .
>
|
|
Also BTW the issue template is meant to be filled out. When opening issues please edit the default message that automatically populated in the issue box and fill out your information and use the Preview tab to see that it looks right before submitting. Here is an example: Describe the bug To Reproduce
Expected behavior Screenshots System (please complete the following information):
|
|
sorry, i'm new to this
…On Thu, Jun 21, 2018 at 9:15 AM Eric Nemchik ***@***.***> wrote:
Also BTW the issue template is meant to be filled out. When opening issues
please edit the default message that automatically populated in the issue
box and fill out your information and use the Preview tab to see that it
looks right before submitting. Here is an example:
------------------------------
*Describe the bug*
I get an error message when trying to run docker-compose up -d
*To Reproduce*
Steps to reproduce the behavior:
1. Run bash ~/.docker/main.sh -g
2. Answer no when asked to run containers now
3. Run cd ~/.docker/compose
4. Run docker-compose up -d
5. See an error message:
couldn't connect to Docker daemon at http+docker://localhost - is it running? If it's at a non-standard location, specify the URL with the DOCKER_Host environment variable
*Expected behavior*
Containers should start.
*Screenshots*
(You can remove sections that do not apply, in this case copying the error
message covers you better than showing a screenshot)
*System (please complete the following information):*
- OS: Ubuntu Desktop x64
- Version 18.04
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQqVGXQiptasWzE4NbgD5xq9pAED-ks5t-5yNgaJpZM4UyAU2>
.
|
|
No problem. Can you post the full log of what happens when you run |
|
mcmike@mcmikeU:~$ sudo bash ~/.docker/main.sh -i
[sudo] password for mcmike:
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2
kB]
Hit:3 https://download.docker.com/linux/ubuntu bionic
InRelease
Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2
kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6
kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11
Metadata [112 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48
Icons [25.1 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64
Icons [44.5 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11
48x48 Icons [120 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11
64x64 Icons [192 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu bionic-backports/universe amd64
DEP-11 Metadata [5,100 B]
Get:12 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11
Metadata [204 B]
Get:13 http://security.ubuntu.com/ubuntu bionic-security/universe amd64
DEP-11 Metadata [2,452 B]
Fetched 743 kB in 1s (515 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 604 0 604 0 0 1230 0 --:--:-- --:--:-- --:--:--
1227
100 5259k 100 5259k 0 0 481k 0 0:00:10 0:00:10 --:--:--
844k
# Executing docker install script, commit: 36b78b2
Warning: the "docker" command appears to already exist on this system.
If you already have Docker installed, this script can cause trouble, which
is
why we're displaying this warning and provide the opportunity to cancel the
installation.
If you installed the current Docker package using this script and are using
it
again to update Docker, you can safely ignore this message.
You may press Ctrl+C now to abort this script.
+ sleep 20
+ sh -c apt-get update -qq >/dev/null
+ sh -c apt-get install -y -qq apt-transport-https ca-certificates curl
/dev/null
+ sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key
add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu
bionic edge" > /etc/apt/sources.list.d/docker.list
+ [ ubuntu = debian ]
+ sh -c apt-get update -qq >/dev/null
+ sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
+ sh -c docker version
Client:
Version: 18.05.0-ce
API version: 1.37
Go version: go1.9.5
Git commit: f150324
Built: Wed May 9 22:16:13 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.05.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: f150324
Built: Wed May 9 22:14:23 2018
OS/Arch: linux/amd64
Experimental: false
If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:
sudo usermod -aG docker your-user
Remember that you will have to log out and back in for this to take effect!
WARNING: Adding a user to the "docker" group will grant the ability to run
containers which can be used to obtain root privileges on the
docker host.
Refer to
https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
for more information.
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 12211 100 12211 0 0 28463 0 --:--:-- --:--:-- --:--:--
28397
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 617 0 617 0 0 1214 0 --:--:-- --:--:-- --:--:--
1212
100 10.3M 100 10.3M 0 0 1021k 0 0:00:10 0:00:10 --:--:--
478k
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 13043 100 13043 0 0 44363 0 --:--:-- --:--:-- --:--:--
44515
groupadd: group 'docker' already exists
Synchronizing state of docker.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
Your system needs to reboot for changes to take effect. Would you like to
reboot now? [Yn]
…On Thu, Jun 21, 2018 at 9:29 AM Eric Nemchik ***@***.***> wrote:
No problem. Can you post the full log of what happens when you run sudo
bash ~/.docker/main.sh -i?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQou2ULci-pAhZGfuswSrifTFbDF4ks5t-5_UgaJpZM4UyAU2>
.
|
|
That all looks good to me. Can you try |
|
Also, say yes at the prompt to bring up the containers (it will run |
|
mcmike@mcmikeU:~$ sudo bash ~/.docker/main.sh -g
[sudo] password for mcmike:
Sorry, try again.
[sudo] password for mcmike:
Could not find
/home/mcmike/.docker/compose/.apps/watchtower/watchtower.ports.yml file.
Would you like to run your selected containers now? [Yn]y
couchpotato is up-to-date
ombi is up-to-date
organizr is up-to-date
nzbget is up-to-date
radarr is up-to-date
sabnzbd is up-to-date
watchtower is up-to-date
deluge is up-to-date
hydra2 is up-to-date
transmission is up-to-date
plex is up-to-date
portainer is up-to-date
tautulli is up-to-date
…On Thu, Jun 21, 2018 at 9:46 AM Eric Nemchik ***@***.***> wrote:
Also, say yes at the prompt to bring up the containers (it will run docker-compose
up -d for you)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQt3nqldfn5srOkkusaipL3hFMdSCks5t-6OqgaJpZM4UyAU2>
.
|
|
That looks like it's working. if you use the script and answer yes to running your containers you don't need to run |
|
Also could you try running I think it's only really an issue if you try running |
|
I get the same error message when I run without using sudo. no error with
sudo.
…On Thu, Jun 21, 2018 at 10:38 AM Eric Nemchik ***@***.***> wrote:
Also could you try running bash ~/.docker/main.sh -g without sudo?
I think it's only really an issue if you try running docker-compose up -d
by itself without sudo. I think the main script works without sudo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQu4R-V-LTLcM7g44DL85ICNAmmrhks5t-6_QgaJpZM4UyAU2>
.
|
|
You mean running |
|
yes
…On Thu, Jun 21, 2018 at 12:09 PM Eric Nemchik ***@***.***> wrote:
You mean running bash ~/.docker/main.sh -g without sudo gives you the
error?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQCpQpKJYbYz8e8URIeUngY32RD4XYbNks5t-8UrgaJpZM4UyAU2>
.
|
|
sorry for the slow response. I am struggling with Organizr and I cannot get
Sabnzb on port 9090
…On Thu, Jun 21, 2018 at 12:59 PM Mike McMichael ***@***.***> wrote:
yes
On Thu, Jun 21, 2018 at 12:09 PM Eric Nemchik ***@***.***>
wrote:
> You mean running bash ~/.docker/main.sh -g without sudo gives you the
> error?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#52 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQCpQpKJYbYz8e8URIeUngY32RD4XYbNks5t-8UrgaJpZM4UyAU2>
> .
>
|
|
Why don't you join us on gitter https://gitter.im/GhostWriters/DockSTARTer We might be able to help with scattered issues on there a little better. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: