apiman
Replies: 4 comments 11 replies
-
|
Hello, link here https://www.apiman.io/apiman-docs/installation-guide/3.0.0-SNAPSHOT/quickstart.html to download docker compose files is broken. Also apiman/apiman-docker#106 . |
Beta Was this translation helpful? Give feedback.
-
|
This hasn't been released yet. It will work when Apiman 3 is out. As I'm trying to juggle so many different things, the release has been delayed until I can create the new website and several other things. |
Beta Was this translation helpful? Give feedback.
-
|
@Kazun3500 Apiman 3 is out now — please try the quickstart when you have time. |
Beta Was this translation helpful? Give feedback.
-
|
Helou! Apiman its fantastic! Congratulations, I'm not an English native speaker/writer, I apologize about mistakes that I can probably do. Today I've been trying to up apiman with docker-compose quickstart. I've tried to up in a test server that runs docker on Debian Bullseye (Debian 11) First problem Second problem: Then tried to acces to apiman ui from my windows pc. I could see apimanui to keycloak redirection and keycloak login But then when I've just logged in, I saw a 500 error in gui (no matter which link or button have been clicked).
I've searched for errors into apiman-manager docker log: I didn't found evindences. Then I've searched for errors into apiman-gatewat log: I've found ES errors (related down) I 've also searched at postgres and I found more errrors: |
Beta Was this translation helpful? Give feedback.
-
Yes I executed dockercompse-setup: keys/certs was created in ../data/keys folder based on secrets in .env file For the ulimit ... Is it about host machine or about keycloak container? |
Beta Was this translation helpful? Give feedback.
-
I also suspect that local.gd it's might breaking things. I want to use quickstart as I used to do in older versions( with the all in one docker). I have to create a lab server to test apiman, but not in a local machine, because others has to test it. I love it new aproach: break each component into a service container. We didn't have traefik in old all in one container. I want to resolve with ips or with a static domain rule in hosts or similar files in computers that act as a clients. I'm not sure If I change .env variable APIMAN_HOSTNAME It will run, just because reverse_proxy (traefik) has rules that need a subdomain to be efective. Browser console:
Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
|
There is no all-in-one Docker image any more as Keycloak Server does not support being co-hosted with another application. It must be run independently. Try binding to a real hostname instead of local.gd in You could also look at changing: APIMAN_GATEWAY_PUBLIC_ENDPOINT=http://gateway.${APIMAN_HOSTNAME}:${HTTP_PORT}
APIMAN_MANAGER_UI_ENDPOINT=http://apiman.${APIMAN_HOSTNAME}:${HTTP_PORT}/apimanui/api-manager/
APIMAN_MANAGER_API_ENDPOINT=http://apiman.${APIMAN_HOSTNAME}:${HTTP_PORT}/apiman
KEYCLOAK_PUBLIC_ENDPOINT=http://auth.${APIMAN_HOSTNAME}:${HTTP_PORT}
KEYCLOAK_PRIVATE_ENDPOINT=http://keycloak:8080You should have an adequate ulimit set on both host and container. Please paste errors into a triple backtick code block, otherwise it can be difficult to read ``` |
Beta Was this translation helpful? Give feedback.
-
Sure, that's what a I want: Docker stack with indepenedent services. Great job on that way, thanks.
I just have edited my hostname in server, and I've mapped new name in hosts in my windows client. I can reach server by server names. I've changed .env, and I've changed ulimit for host (container have a rule in docker-compose.yml for that). Only as a beta tester:
gateway container message Browser error: Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, the information you have provided is not enough for me to figure it out. I suggest you use the network tab and inspect the response that fails, and it should provide some information. It sounds like the UI is unable to reach the backend, or similar.
You need to do a
This indicates the Apiman Gateway is trying to connect to Elasticsearch internally within the Docker network where the container is called "elasticsearch". This means your Elasticsearch instance probably did not start properly, and you should inspect the Elasticsearch container to see what the logs say, e.g. Check the logs for the Apiman manager also and see whether there is something wrong.
|
Beta Was this translation helpful? Give feedback.
-
|
I've found my mistake:
Now all it works, but I cant' view maildev ui nor receive elasticsearch responses from his respective endpoints (those related on documentation). Next, i've to migrate my 2.1 installation to 3.0.0 new docker compose installation. Thanks Marc! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for providing an update.
Thanks, I'm not sure what the minimum version of Docker and/or Docker Compose are that will work (other than the ones specified in the file, of course). Maybe I can make a note on the website
Yes, definitely. It's better/simpler to just use the official download. If you build your own, then you need to build apiman and apiman-docker with Maven first to resolve all the dependencies I included in the docker-compose distro.
Not sure what the problem is with maildev. That works OK for me. If you have any ideas, then happy to hear it. With Elasticsearch, it looks like something might have changed since I first created the docker-compose that means the external routing there isn't quite working right (or maybe I made a typo in the docs). I will try to correct that for 3.1.0.Final. Thank you.
|
Beta Was this translation helpful? Give feedback.
-
|
I've also been thinking it might be nice to figure out a way to have an 'init container' instead of separate docker compose file. This will make things a bit simpler, I think. |
Beta Was this translation helpful? Give feedback.
-
|
Hey thanks for APIman. I have tried install and run with another port 8080-> 8000 (changed in .env). But when i connect to http://apiman.local.gd:8000/apimanui i have error 502. I retried without change ports and they work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The Apiman Docker Compose distro is new in Apiman 3.
Please let me know what you think, how I could improve it, and any other suggestions you may have.
Did you find it useful?
Did you have any problems?
Beta Was this translation helpful? Give feedback.
All reactions