This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-27
Channels
- # aleph (2)
- # beginners (19)
- # boot (15)
- # cider (1)
- # cljsrn (1)
- # clojure (68)
- # clojure-austin (12)
- # clojure-dev (2)
- # clojure-france (6)
- # clojure-italy (46)
- # clojure-russia (45)
- # clojure-spec (55)
- # clojure-uk (41)
- # clojurescript (117)
- # component (15)
- # cursive (54)
- # datomic (24)
- # events (2)
- # funcool (1)
- # instaparse (4)
- # klipse (30)
- # lein-figwheel (3)
- # leiningen (4)
- # luminus (4)
- # om (10)
- # onyx (13)
- # parinfer (36)
- # proton (1)
- # reagent (1)
- # ring (2)
- # ring-swagger (1)
- # rum (19)
- # test-check (6)
- # testing (9)
- # untangled (1)
Morning Folks
So, @agile_geek I put together a Dockerfile (see conversation yesterday) and I have fallen at the last hurdle⌠The container image builds, no problem, but when I run the image I get this: "docker: Error response from daemon: oci runtime error: exec: "/code": permission denied.â I fear that I am doing something obviously wrong...
Dockerfile:
FROM openjdk:8-alpine
MAINTAINER C. Oliver Godby <[email protected]>
RUN mkdir /code
RUN mkdir /code/toggler-configs
ADD ./config.json /code/toggler-configs
ADD ./target/toggler-1.1.4-standalone.jar /code
EXPOSE 7000
ENTRYPOINT ["/code"]
CMD ["java -jar toggler-1.1.4-standalone.jar /code/toggler-configs/â]
Two mins...
This is what we are using in current client:
FROM openjdk:8-alpine
ADD target/xxxx.com.jar /opt/xxxx.com.jar
ADD run-server.sh run-server.sh
RUN chmod +x run-server.sh
CMD ["/bin/sh", "/run-server.sh"]
[in run-server.sh]
#!/bin/sh
java -Xmx2048m -Xms512m -jar /opt/xxxx.com.jar
super simple. I didn't do the Docker stuff and I'm no expert on it but this might give you a start?I suspect ENTRYPOINT
needs to be a command - a bash script?
I think that you may be correct - that is what I am trying now based on your advice ^^
My bad - I am used to Docker Compose and forgot to manually bind the local port for it when I ran the container on its own.
Thanks so much @agile_geek - adding the shell script to run the .jar was all it took.
@maleghast you're welcome
I really wish I could do more with Clojure, but itâs not something that I can teach everyone here to use - donât have time, or willing coders. There is a very odd âI donât want to learn new stuffâ mentality out here in Manila...
However, I can sneak it onto the stack as a service that the team are just going to use, having forked it from my personal repo.
I don't think it's a Manila thing...I see it in the UK just as much. It's definitely a large corporate thing but not exclusively. I see a lot of ppl who just want to do their 9 to 5 and that's it, but even in the Java or .NET communities their are ppl who are enthused about learning, just look at the size of the LJC.
I think we are spoilt in the Clojure community as it almost self selects ppl who are interested in learning and moving forward... to the point that we have Clojurians moving on to Elm, etc.
Morning @jonpither
@agile_geek - You know what, you may be right. I think itâs exaggerated here; if you have 4-6 years of any tech under your belt here then you can reasonably expect to move up the ladder, get into a âgood jobâ and learning new things, being disruptive is not what people want, they want you on your game with your 6 years of PHP or whatever...
@jonpither I bet you are - was it good?
@agile_geek totally agree
@jonpither I am going to TRY to look at Spec⌠I feel as though it will be a game changer like core.async was, except more so, but I am going to have to struggle to find the time.
If I donât put it at the top of all my lists I wonât get to it⌠Python is taking over my professional life (could be a LOT worse), and I am still trying to find time for my side-project, to get it beyond architecture and write some code...
So maybe clojure.spec is the way to do that - they always say itâs good to have a project on which to use the thing you want to learn⌠đ
on the spec front, i discovered an interesting factoid in some of our stuff. spec/tuple is ~5 times quicker than spec/cat. So, i'd say, only use cat if you really really want the destructing, if your just doing some validation, then tuple is your man!