kompose | Convert Compose to Kubernetes | Continuous Deployment library

Yes you can use the host path or you can use the emptydir that's on you

Probably hostpath would be a better option.

If you are planning to use the minikube you can also check out the PV and PVC option which is mostly for the persistence storage in Kubernetes.

Hostpath : https://kubernetes.io/docs/concepts/storage/volumes/#hostpath-configuration-example

emptydir : https://kubernetes.io/docs/concepts/storage/volumes/#emptydir

Posting the answer out of comments.

First what kubectl proxy is:

Creates a proxy server or application-level gateway between localhost and the Kubernetes API server. It also allows serving static content over specified HTTP path. All incoming data enters through one port and gets forwarded to the remote Kubernetes API server port, except for the path matching the static content path.

Also kubectl proxy works with HTTP requests, it does not work with TCP traffic. (this is probably the reason why it did not work).

You can read more in a good answer - kubectl proxy vs kubectl port-forward

Common options to access the service inside the cluster are:

• use kubectl port-forward - for local development and testing purposes

• use loadbalancer or nodeport service type - more advanced options which can be used across clusters and production environments. Find more about service types.

In this case, you can try to restart your deployment:

After kompose convert your flower-service.yaml file have duplicate ports - that's what the error is saying.

In a comment you write:

When I want to delete all, I run this command:

It came up that image contains rabbitmq-diagnostics but when you will specify command as a single string like that, it's looking for a binary in the path that's literally the full string, including spaces, rabbitmq-diagnostics -q ping, so it should be something like this instead:

You trying to access consul with localhost from NestJs service, this is another container, it's localhost is different from consul localhost, you need to access consule with the container name as the host

Change consul host to ${{ CONSUL_HOST }} in bootstrap-development.yaml.

CONSUL_HOST is defined in docker-compose.yaml: CONSUL_HOST=consul

new bootstrap-development.yaml:

Hi - I found the root cause of the problem - and answered the question yesterday night - but my post was deleted - not sure why (possibly since I hadn't finished registration???)

Turns out that the root of the problem is because the default Dockerfile image does NOT have the modules included. These modules seem to be downloaded after the first successful login (which interestingly requires the setup to finish - catch-22)!!!

Fix:

• Download the following 3 modules from their Github - offline-payments, paypal-standard and bc21.
• Extract the contents of these to 3 folders to the akaunting-modules volume - folder names need to be OfflinePayments, PaypalStandard and BC21 (guessing case sensitive).
• Restart the containers.

Let me know if that helps. I've got to the Wizard steps by doing the above. After you pass the Wizard steps remember to restart with AKAUNTING_SETUP=false (checks for existing records don't seem to be great) R. Saravanan

The issue is that Volumes are not behaving the same way in Docker in docker-compose and K8s. Kompose can't perfectly translate volume. In Docker with docker-compose, your declared volume keep the existing files from the directory, while in k8s, a volume is created empty and shadow the existing content.

There is no direct equivalent of docker-compose volumes that keeps existing files in k8s, you will have to work around that with one of the following options, depending on what makes sense in your use case:

• leverage ConfigMaps to add your files to this app volume (if needed, use subPath). Probably ok for a handfull of config files if that's what lives your app directory when the container starts
• in your dockerfile, use COPY to something like app-tmp, then in your entrypoint script copy those files from that app-tmp directory to your "app" volume
• Refactor your application so that it uses "app1" directory (without volumes) with existing files, "app2" starts empty and is used as your volume.