Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] failed to start Pouch Daemon #45

Closed
allencloud opened this issue Nov 3, 2017 · 2 comments · Fixed by #68
Closed

[bug] failed to start Pouch Daemon #45

allencloud opened this issue Nov 3, 2017 · 2 comments · Fixed by #68
Assignees
Labels
areas/daemon kind/bug This is bug report for project

Comments

@allencloud
Copy link
Collaborator

allencloud commented Nov 3, 2017

Issue Description

When I run Pouch Daemon on linux machine, I ran into such as a situation:

root@ubuntu:~/go/src/github.com/alibaba/pouch# ./pouchd
ERRO[2017-11-03 15:55:04.312329177] failed to new containerd's client: failed to connect containerd: failed to dial "/var/run/containerd.sock": dial unix /var/run/containerd.sock: connect: connection refused
ERRO[2017-11-03 15:55:04.317246405] failed to wait process: /usr/local/bin/containerd, signal: killed
WARN[2017-11-03 15:55:04.317710458] process: /usr/local/bin/containerd exited
Error: failed to new daemon
Usage:
   [flags]

Flags:
  -c, --containerd string          where does containerd listened on (default "/var/run/containerd.sock")
      --containerd-config string   Specify the path of Containerd binary (default "/etc/containerd/config.toml")
      --containerd-path string     Specify the path of Containerd binary (default "/usr/local/bin/containerd")
  -D, --debug                      switch debug level
  -h, --help                       help for this command
      --home-dir string            The pouchd's home directory (default "/etc/pouchd")
  -l, --listen stringArray         which address to listen on (default [unix:///var/run/pouchd.sock])

It seems that the inner config to setup between pouchd and containerd causes this error.
In addition, I was confused that when pouch daemon met an error, it would throw out the following things:

Usage:
   [flags]

Flags:
  -c, --containerd string          where does containerd listened on (default "/var/run/containerd.sock")
      --containerd-config string   Specify the path of Containerd binary (default "/etc/containerd/config.toml")
      --containerd-path string     Specify the path of Containerd binary (default "/usr/local/bin/containerd")
  -D, --debug                      switch debug level
  -h, --help                       help for this command
      --home-dir string            The pouchd's home directory (default "/etc/pouchd")
  -l, --listen stringArray         which address to listen on (default [unix:///var/run/pouchd.sock])

Describe what happened:
Pouchd failed to start up.

Describe what you expected to happen:
Pouch works to start up.

How to reproduce it (as minimally and precisely as possible):

  1. build pouchd binary via make build
  2. execute ./pouchd

Anything else we need to know?:
NONE

Environment:

@allencloud allencloud added kind/bug This is bug report for project areas/daemon labels Nov 3, 2017
@allencloud allencloud added the kind/bug This is bug report for project label Nov 3, 2017
@Ace-Tang
Copy link
Contributor

Ace-Tang commented Nov 3, 2017

how about do a config file for pouch? ping @allencloud @skoo87

@allencloud
Copy link
Collaborator Author

Can't agree more @Ace-Tang
If you are determined to do that, please first open a proposal issue and start to work on that.
Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
areas/daemon kind/bug This is bug report for project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants