fabric8

I have a JBoss Fuse running on OpenShift Online and I want to deploy there a Camel-CXF application. I created a profile and attached it to a running container. When I added a feature-camel parent to this profile, the container was successfully restarted, but then I tried to add feature-cxf the container failed with the following errors: io.fabric8.agent.utils.MultiException: Error while downloading artifacts java.util.zip.ZipException: zip file is empty When I tried to add any features related to cxf I had the same errors. What can be the problem and how can it be resolved? Thanks, Anton 来源：

Running mvn clean install pulls up this error( Windows) [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.20.1:start (prepare-environment) on project integration-test: Execution prepare-environment of goal io.fabric8:docker-maven-plugin:0.20.1:start failed: Start-Job failed with unexpected exception: [sebp/elk:latest] "elk": Timeout after 120365 ms while waiting on url http://localhost:32774/ 来源： https://stackoverflow.com/questions/44226315/failed-to-execute-fabric8-docker-plugin

we have developped application based on Karaf and Apache Camel. While our application is entirely based on bundles ( OSGI ) we are also loading the Camel context ( and its' Route Contexts ) on startup, whcih would mean that we have defined some static routes. My question is. Is there a way to dynamically LOAD routes while the application is running without the need to reread the Camel Context as this will reset/restart the already existing routes. The same would apply to already created routes, for example if we want to edit a route whcih already exist. The whole idea is that we are planning

Is there a way to programmatically get the name of the pod that a container belongs to in Kubernetes? If so how? I'm using fabric8's java client but curl or something similar will be fine as well. Note that I don't want to find the pod using a specific label since then (I assume) I may not always find the right pod if it's scaled with a replication controller. You can tell Kubernetes to put the pod name in an environment variable of your choice using the downward API . For example: apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: gcr.io