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

Snap setup (can't access) doesn't appear in port 3000 #366

Open
Apperator opened this issue Mar 6, 2018 · 1 comment
Labels
bug
Milestone

Comments

@Apperator
Copy link

@Apperator Apperator commented Mar 6, 2018

Fresh Ubuntu 16.04

Snap installed
snap install convos

Can't access convos in browser. Port 3000 and localhost don't return anything.

@marcusramberg marcusramberg added the bug label Mar 6, 2018
@Nordaaker Nordaaker deleted a comment from marcusramberg Oct 27, 2019
@Nordaaker Nordaaker deleted a comment from marcusramberg Oct 27, 2019
@jhthorsen jhthorsen added this to the Backlog milestone Oct 27, 2019
@jhthorsen

This comment has been minimized.

Copy link
Member

@jhthorsen jhthorsen commented Oct 27, 2019

I'm not sure what's going on... I tried to build a snap for the 1.00 release, but I'm unable to:

$ bash ./snap/build.sh 
+ snap list convos
error: no matching snaps installed
+ sudo snapcraft cleanbuild
Creating snapcraft-oddly-moving-gull
Starting snapcraft-oddly-moving-gull
error: flag provided but not defined: --format
Failed to get container image info: `lxc image list --format=json ubuntu:xenial/amd64` returned with exit code 2, output: b''
It will not be recorded in manifest.
Waiting for a network connection...
Failed to open 'http://start.ubuntu.com/connectivity-check.html': timed out
Failed to open 'http://start.ubuntu.com/connectivity-check.html': timed out
Failed to open 'http://start.ubuntu.com/connectivity-check.html': timed out
Failed to open 'http://start.ubuntu.com/connectivity-check.html': timed out
Failed to open 'http://start.ubuntu.com/connectivity-check.html': timed out
Stopping local:snapcraft-oddly-moving-gull
Failed to get a network connection in the container: could not successfully ping 'start.ubuntu.com'.
If using a proxy, check its configuration. Refer to the documentation at https://linuxcontainers.org/lxd/getting-started-cli.

Do you know what's going on? The server has access to internet, and I can curl http://start.ubuntu.com/connectivity-check.html from the command line.

jhthorsen added a commit that referenced this issue Oct 27, 2019
jhthorsen added a commit that referenced this issue Oct 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.