mikelangelo-project / capstan-packages Goto Github PK

Hi,
I am trying to build image based on node-6.10.2. But by default it is taking node-4.4.5 also (for runtime node).
And while executing the the main js file, it is executing with 4.4.5 version instead of 6.10.2 version.

• Both node binary of version 4.4.5 & 6.10.2 are available in mpm-pkg/bin directory.
• node symbolic link in mpm-pkg directory is pointing to /bin/libnode-4.4.5.so

I have created node (symbolic link file) points to '/bin/libnode-6.10.2.so' file. I am getting the following error,
symlink /bin/libnode-6.10.2.so /home/ukesh/code/mpm-pkg/node: file exists

I am using the below,

• Capstan binary : http://x.k00.fr/3ub70 ->this is the latest Capstan binary (development branch)
• Packages downloaded using 'capstan pull' command

Could you please help me to resolve this issue ?

Hi,
so far, a good use case I see for Mikelangelo is the development in Java/Python/NodeJS with your precompiled packages but I am exploring the recipe part for a EU project.

I need a clarification about the workflow to create new MPM packages.
According to this post, I have to use a Docker image for the building and, from this picture, it seems I can install the apt packages I need (BTW, go/capstan is ok, but why Java is needed in this phase?)

1st question is if about these apt packages: they will not be available in the final package and they are mentioned only to support the building, right?

2nd: if I needed an unikernel image with iptables, I should refer to the OSv apps examples and download the .so or build them from source, just like the Python examples here and here, correct? Basically, I cannot simply do an apt-get install iptables but I have to manage the dependencies, get the related .so and prepare the recipe for that, right?

3rd: from the statement "Preparing a package requires knowledge about the application itself as well as the OSv limitations" I should be also aware of the limitations of the application I am going to build (I guess for example no usage of fork(), exec(), etc.). Where could I found more details on these limitations? Just to understand if and how an existing app could be ported on unikernel, although I see there are many interesting examples available.

Thanks in advance for the help provided.

BR
Francesco

I trying to do capstan build for a Maven project in EC2 but while composing the image file I am getting the below error .
I have followed the below steps
wget -O - https://raw.githubusercontent.com/mikelangelo-project/capstan/master/scripts/download | bash
capstan pull mike/osv-loader

Can you please help me .
Resolved runtime into: java
Prepending 'java' runtime dependencies to dep list: [eu.mikelangelo-project.osv.java]
package eu.mikelangelo-project.osv.java is not available in the given repository (https://mikelangelo-capstan.s3.amazonaws.com/)

I am building a C native application that has a runtime dependencies with application config-file and the License file (and some environment variables). I have created the shared object, and run.yaml has only limited options,

runtime: native
config_set:
   ################################################################
   ### This is one configuration set (feel free to rename it).  ###
   ################################################################
   myconfig1:
      # REQUIRED
      # Command to be executed in OSv.
      # Note that package root will correspond to filesystem root (/) in OSv image.
      # Example value: /usr/bin/simpleFoam.so -help
      bootcmd: /my_client.so

   # Add as many named configurations as you need
# OPTIONAL
# What config_set should be used as default.
# This value can be overwritten with --runconfig argument.
config_set_default: myconfig1 

So, How to add the application environment variables (License file and config files etc..,)

I have a Java with Maven project with all dependencies ,I have done mvn package and trying to run the main class but it could not able to resolve the dependencies can you please provide the steps to run the maven project with all dependencies.