Assuming you have Docker installed, this will pull the latest all-in-one image from DockerHub, and start it listening on :7777.

##### The following command will pull and run the latest stable image. 
### Remove the -v option if you do not need to preserve your projects between runs
##
docker run -e LANG=C.UTF-8 --memory=8g -p 0.0.0.0:7777:7777 -it "intrigueio/intrigue-core:latest"

Once downloaded, you’ll see the startup happen automatically, and a password will be generated for you. You’ll be able to access the interface on :7777 on your local host, since you forwarded the port to localhost.

Now that you have an instance running, check out the Up and Running with Intrigue Core guide.

Quick Docker image FAQ:

THE SERVICE IS NOT LOADING ON :7777: Did you forward the port when starting the container (as the example above does?) Make sure to access it using HTTPS, there is a certificate generated at start time! If you’re still having trouble, try opening a shell on the docker container using docker exec

docker exec -it <CONTAINER_ID> /bin/sh)

and make sure the service is actually running on :7777 (using something like netstat -lnt). If it is running in the container, than everything is working as expected, and the problem is very likely with your host system’s networking settings.

I’M ON A SMALLER SYSTEM AND AM EXPERIENCING INSTABILITY: Running Core is memory and CPU intensive, and you’ll want to make sure your Docker daemon has access to enough RAM. While you can start the container. with the –memory= flag above, if you have not given the Docker daemon itself enough RAM, it wont work. See this link for more assistance on how to accomplish this.

I’D LIKE TO PRESERVE DATA BETWEEN RUNS, CAN YOU HELP?: In order to preserve your instance data between container runs, you can use Docker’s volume support. If you’d like to do this, simply add the following -v option in the docker run command above, using the syntax LOCAL_FOLDER:/data. An example is below.

-v ~/intrigue-core-data:/data

I’M HAVING ODD PERMISSION ISSUES WHEN TRYING TO LAUNCH THE CONTAINER ON RHEL: If you’re running Docker on a RHEL system as a user other than root, you may need to add the —privileged flag

If you’re still having trouble, jump into our Slack channel and ask questions in #core-help!

4 comments

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s