Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

OSv always prints internal IP but I think it would be nice if scripts/run.py and capstan printed the external ip address (and possibly ports if forwarding) to make it clear to users what is available. On Sunday, March 31, 2019 at 6:42:42 AM UTC-4, robertob wrote: > > Yes, you are right. It was

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Yes, you are right. It was a my mistake. Thanks a lot r Il giorno dom 31 mar 2019 alle ore 11:09 Rick Payne ha scritto: > > > On 31 Mar 2019, at 19:56, roberto battistoni > wrote: > > Sorry but the DHCP offers the IP both in the NAT and BRIDGE configuration. > I think that the "forward"

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

> On 31 Mar 2019, at 19:56, roberto battistoni wrote: > > Sorry but the DHCP offers the IP both in the NAT and BRIDGE configuration. I > think that the "forward" does not work in the bridge configuration. Why would it be forwarding in ‘bridge’ mode? I think you’re slightly confused. In

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Sorry but the DHCP offers the IP both in the NAT and BRIDGE configuration. I think that the "forward" does not work in the bridge configuration. For example: capstan run -n "nat" -f "8000:8000" -e "--verbose /cli/cli.so" uni ==> THIS WORKS and "curl http://localhost:8000/os/version; returns

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

On Thu, 2019-03-28 at 14:20 +0100, roberto battistoni wrote: > [I/211 dhcp]: Received DHCPACK message from DHCP server: > 192.168.122.1 regarding offerred IP address: 192.168.122.168 This is the typical subnet used by libvirt/qemu, and is typically only available locally on the machine unless you

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Sorry I didn't be so clear in my explanation. Running cli.so (with httpserver api) is only a test to understand why are not reachable the REST services. In my case the problem is that with BRIDGE configuration this does not work, instead with NAT it works. I need the BRIDGE configuration for my

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

On Thursday, March 28, 2019 at 3:16:30 AM UTC-4, robertob wrote: > > I did the include step you suggested but it did not work. > > So I made a test: > > capstan run uni -n "nat" -f "8000:8000" -e "/cli/cli.so” > I think order matters so this should be: capstan run -n "nat" -f "8000:8000" -e

Re: [osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

I did the include step you suggested but it did not work. So I made a test: capstan run uni -n "nat" -f "8000:8000" -e "/cli/cli.so” With “nat” configuration I see the REST services from the host (http://localhost:8000/ …), but when I switch to “bridge” I don’t see

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

I have just uploaded newest 0.53.0 packages for API server under https://github.com/cloudius-systems/osv/releases/tag/v0.53.0 (artifacts). Please download and put them under your local .capstan/packages directory. Then add/replace 'requires' section to include

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Now the probem is how to run the Rest server to get the logs inside the image... All the documentation tell me to include "osv.httpserver-api". I have exposed the port 8000 trough the option "-f" for the capstan run, but the port does not answer. This is my cmdline to run the image: "

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Yes, now it works. I read your other messages about how it is frustrating to access the documentation on OSV and I confirm. In general is not easy to understand how to do things and what are the differences with various version of the software. I thank you for your amazing help roberto Il

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Try to replace osv-loader.qemu under ~/.capstan with newer version of kernel - https://github.com/cloudius-systems/osv/releases/download/v0.53.0/osv-loader.qemu. On Sunday, March 24, 2019 at 2:47:36 AM UTC-4, robertob wrote: > > Thank you so much. > > I did all you wrote but I get these

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

Thank you so much. I did all you wrote but I get these lines: OSv v0.24-472-gf240a59 eth0: 192.168.122.15 /java.so: failed looking up symbol _ZTINSt6thread6_StateE (typeinfo for std ::thr [backtrace] 0x003477cd 0x00399922 0x00346247 0x00349cdc

[osv-dev] Re: Problems to pass arguments to a JAR in run.yaml

So I have tested it myself and it looks like capstan (or OSv cannot parse properly command line built by capstan) cannot properly handle arguments when passes through YAML args list. It looks like you are using the "java" runtime that capstan advertises which aims to make it easier to deploy