-
Notifications
You must be signed in to change notification settings - Fork 5
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
"operation not permitted" when trying to use the CLI #11
Comments
Could you try changing |
are you sure that the pipeline is running inside that container? |
Yes I did that earlier (changed to 0.0.0.0 - it should probably be that by default in v1.10) to fix a similar issue I think but it doesn't seem to work now. I'm sure that DP2 is running inside the container. Here's how to reproduce:
|
maybe in the the config.yml file for the client as well? |
Nope. I've now tried localhost, 127.0.0.1, 172.17.0.3 (the containers public IP) and 0.0.0.0 in both system.properties and in config.yml. Same results. I also get the same results if I change the IP or port to something clearly wrong, for instance 1.2.3.4 and 8188:
|
I'm trying to reproduce, so I checked out that project but when running
|
Maybe mod-celia v1.2.0 isn't staged anymore. @bertfrees do you know? |
Yes they weren't released properly. Can you try 1.8.0? I don't feel like going through the whole process of uploading again right now :( |
I'm getting this error (with debugging enabled in config.yml), not sure if it's something with my networking setup or whatnot (running from a docker container):
The version I'm using is the one bundled in the released pipeline2-1.9-webui_linux.zip.
curl'ing the engine gives a response, so the engine is up:
Has anyone else experienced this problem?
The text was updated successfully, but these errors were encountered: