This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-21
Channels
- # beginners (5)
- # boot (15)
- # capetown (1)
- # chestnut (2)
- # cljs-dev (9)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (190)
- # clojure-brasil (2)
- # clojure-greece (14)
- # clojure-italy (3)
- # clojure-poland (8)
- # clojure-romania (1)
- # clojure-russia (2)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (98)
- # clojure-ukraine (2)
- # clojurescript (65)
- # clojurex (1)
- # core-async (16)
- # cursive (16)
- # datomic (3)
- # defnpodcast (7)
- # emacs (11)
- # funcool (2)
- # hoplon (16)
- # jobs (1)
- # leiningen (4)
- # lumo (9)
- # off-topic (2)
- # om (1)
- # other-languages (1)
- # protorepl (1)
- # re-frame (50)
- # reagent (16)
- # reitit (32)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (73)
- # spacemacs (36)
- # specter (21)
- # sql (6)
- # unrepl (107)
- # untangled (4)
I'm building a jar inside a kubernetes pod (clojure:alpine image) which supposed to have the EC2 instance role permissions to my jars on S3. Still I get this: Could not transfer artifact aaa:bbb:jar:0.1.8 from/to private-releases (
. I'm using [s3-wagon-private "1.3.0"]
plugin. Anyone has experience with this?
I'm using kops and upgraded an existing working cluster to kubernetes 1.8.3. I see the instances kept all the original additional permissions I gave them but it's not respected anymore.
I also tried with k8s 1.6.12 and have the same problem. I've even explicitly set AWS_ACCESS_KEY_ID
and AWS_SECRET_ACCESS_KEY
with export AWS_ACCESS_KEY_ID=...
before running lein uberjar.
I made it work by using clojure:lein-2.7.1-alpine
explicitly instead of the latest lein-2.8.1-alpine
.
If I use clojure:lein-2.8.1-alpine
image I need to use [s3-wagon-private "1.3.1-alpha3"]
for it to work.
aye, it is recommended to use 1.3.1-alpha3
at this point. @danielcompton maybe it's time to do a release 😉
I've published 1.3.1 now