Tino Rusch
Tino Rusch
Yes this would be great. I already patched some manifests because of this issue. I look if I can do something this week, unfortunately I got other stuff to do......
@lucab forgot my question, found the --raw-port PR.
Just my two cents: Another option would be to introduce an "--expose [name=]http,proto=tcp,port=80" like option on app level. This would simply patch the image manifest (or the pod-manifest, not sure...
(github.com/appc/spec/schema/types).PortFromString() is already there and could do the parsing. Then I would simply add that port to the app in the pod-manifest in the end of the run call right...
You could convert the images by yourself and import them directly. At least this is scriptable so you can get your containers up and running. Md Shaiful Islam schrieb am...
I think you could remove this stuff by hand, but this is not a "fix", it's just a workaround. BTW: is there a good reason for you to explicit pull...
You should be able to restrict the memory usage by running the node within a cgroup with restricted resources. I'd recommend using the container image and run it with podman,...
Could somebody sketch out the scope of this "small go program"? I would volunteer to create a draft over the next weekend.
:+1: A helm-less install would be much appreciated.
docker-compose will always set the correct entry in the /etc/hosts file, but it will also generate that hostname randomly.