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

Error message on Ubuntu 16.04 #50

Closed
solarisfire opened this issue Feb 22, 2018 · 9 comments
Closed

Error message on Ubuntu 16.04 #50

solarisfire opened this issue Feb 22, 2018 · 9 comments
Assignees

Comments

@solarisfire
Copy link

Expected Behavior

Dockly should run.

Actual Behavior

root@neo:~# dockly
/usr/local/lib/node_modules/dockly/src/screen.js:36
constructor (utils = new Map()) {
^

SyntaxError: Unexpected token =
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object. (/usr/local/lib/node_modules/dockly/index.js:10:16)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)
root@neo:~# node --version
v4.2.6

Steps to Re-produce the Problem

  1. Install Ubuntu 16.04
  2. Install docker and create some docker containers
  3. Install node, npm & dockly
  4. Run

Context

  • Operating System: Ubuntu
  • Node.js version (run node --version): v4.2.6 (current in Ubuntu 16.04 LTS)
  • Package version: dockly@3.3.1
  • Docker version (run docker --version): Docker version 1.13.1, build 092cba3
  • Is docker installed locally? Yes
  • Do you have containers created? Yes
  • Does this file exists /var/run/docker.sock ? /var/run/docker.sock: socket (yes)
  • Output of docker info:
    Containers: 5
    Running: 5
    Paused: 0
    Stopped: 0
    Images: 6
    Server Version: 1.13.1
    Storage Driver: aufs
    Root Dir: /var/lib/docker/aufs
    Backing Filesystem: extfs
    Dirs: 50
    Dirperm1 Supported: true
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
    Volume: local
    Network: bridge host macvlan null overlay
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
    runc version: N/A (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
    init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
    Security Options:
    apparmor
    seccomp
    Profile: default
    Kernel Version: 4.4.0-112-generic
    Operating System: Ubuntu 16.04.3 LTS
    OSType: linux
    Architecture: x86_64
    CPUs: 4
    Total Memory: 31.32 GiB
    Name: neo
    ID: ***
    Docker Root Dir: /var/lib/docker
    Debug Mode (client): false
    Debug Mode (server): false
    Registry: https://index.docker.io/v1/
    WARNING: No swap limit support
    Experimental: false
    Insecure Registries:
    127.0.0.0/8
    Live Restore Enabled: false
@lirantal
Copy link
Owner

Hey @solarisfire,

We support Node >= 7.6.0
Is it possible for you to upgrade to a more recent version of Node.js like 8?

@lirantal lirantal self-assigned this Feb 22, 2018
@solarisfire
Copy link
Author

Any chance you could put that in the package.json file so idiots like me get stopped at install?

I ended up just running inside a container for now. However it doesn't look quite right with all of the lines being replaced by x's.

I'll upgrade to nodejs 8 a bit later today. It's a bit of a pain on Ubuntu 16.04 as it installs 4.2.6 by default.

@solarisfire
Copy link
Author

dockly

Running in nodejs 8 now. Doesn't look as pretty as the screenshots though :(

@lirantal
Copy link
Owner

lirantal commented Feb 23, 2018

woohoo 🎉 😄
that does look kinda odd though heh

@solarisfire we do have it on the package.json, in the form of:

  "engines": {
    "node": ">=7.6.0"
  },

but not all package managers respect it, or some would just show an warning during install but will still proceed with installing it.

We also show a Node.js version badge on the README but I guess it's easy to miss too.

@lirantal
Copy link
Owner

I'll close for now but please feel free to re-open if there's anything more we can help with.

@theFra985
Copy link

theFra985 commented Mar 3, 2018

Hi,
I've found the "bad graphic" using PuTTY on windows.
Although using the windows cmd (with the linux subsystem) the interface works better!
I don't know if it can be useful but i noticed that so... ¯\_(ツ)_/¯

@lirantal
Copy link
Owner

lirantal commented Mar 3, 2018

thanks! useful to know ;-)

@norweeg
Copy link
Contributor

norweeg commented Sep 28, 2019

@lirantal @theFra985 @solarisfire I have a solution for bad GUI drawing in PuTTY. In your session settings, you need to check the following box:
image

@lirantal
Copy link
Owner

thanks @norweeg 👍✨

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

No branches or pull requests

4 participants