Maybe

I am able to resolve the issue by using correct active virtualBox Driver (Active Dcoker machine) but now stuck on integrating the Ribbon with Eureka. Not able to discover the hello-netflix-oss on Eureka Dahsboard.

Considering App ips are not exposed outside of container but VirtualBox ip so can somebody help me on how we can make change in exising steps to correct the same

Right now asgard.log isn't on stdout which means it wouldn't be consumed by 12-factor app assuming frameworks.

We did this for anything installed via apt-get and some wget's, but not all. Maven central has a different pgp based hash?

Upon running:
docker pull netflixoss/eureka
My console response is:
Using default tag: latest
Error response from daemon: manifest for netflixoss/eureka:latest not found

Where to go from here?

Can we send emails/notifications on a change or while alerting ?

If yes then how ?
Documents states that the docker images doesn't currently support that .

Just wanted to try out exhibitor locally using docker but it does not work for me, at least the GUi is not accessible:

docker run --name exhibitor -p 8080:8080 netflixoss/exhibitor:1.5.2
v1.0
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Exhibitor started [main]
May 30, 2015 9:20:08 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
INFO  org.mortbay.log  Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog [main]
INFO  org.mortbay.log  jetty-1.0 [main]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  State: down [ActivityQueue-0]
May 30, 2015 9:20:10 PM java.util.prefs.FileSystemPreferences$6 run
WARNING: Prefs file removed in background /root/.java/.userPrefs/prefs.xml
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Attempting to stop instance [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Attempting to start/restart ZooKeeper [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  jps didn't find instance - assuming ZK is not running [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Starting in standalone mode [ActivityQueue-0]
ERROR com.netflix.exhibitor.core.activity.ActivityLog  ZooKeeper Server: JMX enabled by default [pool-2-thread-1]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Process started via: /zookeeper/bin/zkServer.sh [ActivityQueue-0]
ERROR com.netflix.exhibitor.core.activity.ActivityLog  ZooKeeper Server: Using config: /zookeeper/bin/../conf/zoo.cfg [pool-2-thread-1]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  ZooKeeper Server: Starting zookeeper ... STARTED [pool-2-thread-2]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  State: serving [ActivityQueue-0]
May 30, 2015 9:20:48 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.9.1 09/14/2011 02:36 PM'
INFO  org.mortbay.log  Started [email protected]:8080 [main]

Afterwards I executed:

docker ps -q | xargs docker inspect --format '{{ .NetworkSettings.IPAddress }}  {{ .Name }} {{ .Config.Image }} {{ .State.Running }} {{ .Id }}' exhibitor
172.17.0.64  /exhibitor netflixoss/exhibitor:1.5.2 true 157d31182eea69ac8dc7363edaa847f6c48a8ef1ab85ad4a14abc768016da70b
172.17.0.64  /exhibitor netflixoss/exhibitor:1.5.2 true 157d31182eea69ac8dc7363edaa847f6c48a8ef1ab85ad4a14abc768016da70b

but curl times out

curl http://172.17.0.64:8080/exhibitor/v1/ui/index.html
curl: (7) Failed connect to 172.17.0.64:8080; Operation timed out

for all Dockerfiles MAINTAINER email address

It seems to me that you can't do a good run of this using boot2docker, not without digging for Tomcat configuration files. The containers run on different internal IPs, and several things use port 8080. So, you can't expose all these services to the host machine (the machine hosting the boot2docker VM). Am I missing something?

For example netflixoss-eureka:1.1.142

Especially for when run on AWS

I am curious why you guys chose to use the Oracle JDK which some would consider license heavy, especially since you accept on behalf of everyone rather than using openjdk or the Azul version of openjdk?

Blocked by:

soabase/exhibitor#224

Hi guys,

I saw that you are not actively maintain the eureka docker image. The actual Eureka version is 1.3.1, whereas the latest release of the eureka is 1.9.25.

I am actively maintaining an updated version here: https://github.com/dinuta/netflixoss-eureka.

I wonder if you can validate & advertise it, for the community since I added some tests and some people are using it.

Thanks,
Catalin

https://repo1.maven.org/maven2/com/netflix/exhibitor/exhibitor-standalone/1.5.2/exhibitor-standalone-1.5.2.pom

Specifically groupid

Are you guys still maintaining these repos? I'd be happy to help if any general assistance is need.

Having to install maven and doing a full maven build is unnecessary. Would be nice if there was a standalone jar build somewhere (cloudbees?)

It is talking to eureka, but never registering

When trying to launch Zuul from Kitematic a user will receive the error:

Tag latest not found in repository docker.io/netflixoss/zuul

I trying to build a docker image using this file: https://github.com/Netflix-Skunkworks/zerotodocker/blob/master/eureka/1.3.1/Dockerfile

On step 4: ADD config.properties /tomcat/webapps/eureka/WEB-INF/classes/config.properties, I'm getting an error "ADD failed: stat /var/lib/docker/tmp/docker-builder171196452/config.properties: no such file or directory"

Follow the Dockerfile that I'm building:

Copyright 2014 Netflix, Inc.

Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License.

You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

FROM netflixoss/tomcat:7.0.64
MAINTAINER Netflix Open Source Development [email protected]

RUN cd /tomcat/webapps &&
mkdir eureka &&
cd eureka &&
wget -q http://repo1.maven.org/maven2/com/netflix/eureka/eureka-server/1.3.1/eureka-server-1.3.1.war &&
jar xf eureka-server-1.3.1.war &&
rm eureka-server-1.3.1.war

CMD ["run"]


I recently started using the netflixoss/eureka:1.3.1 docker image but I'm getting a 400 Bad Request error on all registrations. This issue doesn't seem to exist on 1.1.147, which is very odd.

The error in the response is: {error:'cannot parse request body'}

Here's my POST body:

{
    "instance": {
        "app": "jqservice",
        "hostName": "localhost",
        "ipAddr": "127.0.0.1",
        "port": 8080,
        "vipAddress": "jq.test.something.com",
        "dataCenterInfo": {
            "name": "MyOwn"
        },
        "status": "UP"
    }
}

URL: http://192.168.99.100:8080/eureka/v2/apps/jqservice

Headers:
Content-Type: application/json
Accept: application/json

If I switch back to netflixoss/eureka:1.1.147 the request succeeds with no other changes. Was there any major changes to the request body that I'm missing? I don't see anything in the server log around the bad request when this happens. If there's anything else I should try, let me know. Thanks!

This means we need to map one into the container that is already filled out.

See http://yiyujia.blogspot.com/2014/07/asgard-15-configgroovy-file-format.html