This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-16
Channels
- # announcements (33)
- # atom-editor (1)
- # aws (21)
- # babashka (174)
- # babashka-sci-dev (2)
- # beginners (59)
- # calva (4)
- # chlorine-clover (9)
- # clj-kondo (51)
- # clojars (7)
- # clojure (86)
- # clojure-czech (4)
- # clojure-europe (21)
- # clojure-france (6)
- # clojure-nl (1)
- # clojure-uk (2)
- # conjure (7)
- # core-async (3)
- # core-logic (3)
- # cursive (10)
- # data-science (8)
- # datalevin (14)
- # datomic (12)
- # events (1)
- # fulcro (5)
- # graalvm (10)
- # gratitude (3)
- # honeysql (3)
- # hyperfiddle (3)
- # introduce-yourself (4)
- # joyride (3)
- # leiningen (3)
- # malli (13)
- # minecraft (15)
- # music (1)
- # off-topic (40)
- # pathom (16)
- # polylith (28)
- # portal (25)
- # rdf (15)
- # remote-jobs (3)
- # shadow-cljs (23)
- # specter (1)
- # sql (5)
- # tools-deps (25)
- # xtdb (31)
Following the upgrade to Datomic Cloud 973-9132, when pushing ions, :dependency-conflicts
are reported as if the cluster ran on e.g. clojure 1.10, which is certainly false.
From experience, this is a false (static) signal due to the absence of a new accompanying release of ion-dev, right?
So it's safe to assume it's OK to use clojure 1.11 even though it tells me it's overwritten back to 1.10, right?
@U0514DPR7, using an older ion-dev will show 1.10 as the dep conflict. The cloud compute nodes are using Clojure 1.11.0 in the latest release.
Thanks for the confirmation, Joe.
having trouble connecting to datomic running in docker
docker run -p 4334:4334 --rm -t datomic
Launching with Java options -server -Xms1g -Xmx1g -Ddatomic.printConnectionInfo=true
Starting datomic: <DB-NAME>, storing data in: data ...
System started datomic: <DB-NAME>, storing data in: data
(d/create-database "datomic:")
=> org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 0.0.0.0:4335" [90067-171]
If I run the container with --net host
however, it works.
I have no idea why. Is there any gotcha I'm missing when it comes to datomic in docker?
I think I've made a bit of progress, the 4335 port wasn't published.
I've made sure to publish all ports using: docker run -p 4334:4334 -p 4335:4335 -p 4336:4336 --rm -t datomic
Now I get this error instead:
main] WARN datomic.coordination - {:event :coord/lookup-endpoint-failed, :pid 196831, :tid 1}
java.util.concurrent.ExecutionException: org.h2.jdbc.JdbcSQLException: Remote connections to this server are not allowed, see -tcpAllowOthers [90117-171]
You're almost there, the H2 server used for local dev only allows https://docs.datomic.com/on-prem/configuration/configuring-embedded-storage.html#local-dev-convenience. Follow the instructions in that page to set passwords and enable remote access.
The reason it works with host networking is because that puts your docker container on the same host, so the default of local connections only still works.