Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Docker fails to init #2018

Closed
KeithSSmith opened this issue May 4, 2019 · 4 comments
Closed

Docker fails to init #2018

KeithSSmith opened this issue May 4, 2019 · 4 comments

Comments

@KeithSSmith
Copy link

  • Version: latest
  • Platform: Dockerfile
  • Subsystem: Node 9.5.0

Type:

Bug

Severity:

High b/c container fails to start

Description:

Attempting to run a Docker instance on my Linux server and when I issue the recommended command the Dockerfile is unable to initialize the IPFS instance and returns Unexpected token * this in turn fails to create the config file that is required to start the daemon and reports issues from the init_and_daemon.sh bash script.

Steps to reproduce the error:

$ docker run -it -p 4002:4002 -p 4003:4003 -p 5002:5002 -p 9090:9090 ipfs/js-ipfs:latest
Using /root/.jsipfs as IPFS repository
initializing ipfs node at /root/.jsipfs
Unexpected token *
sed: can't read /root/.jsipfs/config: No such file or directory
@bleonard252
Copy link

I doubt this issue is solely Docker related. When I'm require()ing it in NodeJS it crashes with the same error.

@gil-air-may
Copy link

Experiencing the same Unexpected token *

@alanshaw
Copy link
Member

alanshaw commented May 9, 2019

Node.js 10 is the current minimum compatible version

@alanshaw alanshaw closed this as completed May 9, 2019
@area
Copy link

area commented Jun 13, 2019

So why is the latest docker image built on Node 9.5?

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

5 participants