<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Datomic Knowledgebase - Recent questions tagged s3 repo</title>
<link>https://ask.datomic.com/index.php/tag/s3%20repo</link>
<description>Powered by Question2Answer</description>
<item>
<title>Could not find artifact com.datomic:ion:jar:0.9.48 in central</title>
<link>https://ask.datomic.com/index.php/546/could-not-find-artifact-com-datomic-ion-jar-0-9-48-in-central</link>
<description>&lt;p&gt;I&#039;m running a Clojure service inside a Docker container, and have the SOCKS proxy configured to give me a connection to a Datomic Cloud system. I verified this setup by creating a database successfully yesterday.&lt;/p&gt;
&lt;p&gt;Unfortunately, this morning when I added a new dependency to the service I had to rebuild the Docker container, and encountered the following error:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Downloading: com/datomic/ion/0.9.48/ion-0.9.48.jar from datomic-cloud
Error building classpath. Could not find artifact com.datomic:ion:jar:0.9.48 in central (https://repo1.maven.org/maven2/)
ERROR: Service &#039;clojure&#039; failed to build : The command &#039;/bin/sh -c clojure -A:dev:test:cider-clj:exit&#039; returned a non-zero code: 1
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I can &lt;code&gt;aws s3 cp&lt;/code&gt; the JAR from the S3 bucket just fine but Maven isn&#039;t as cooperative. I do have an explicit AWS access key exported inside the Docker container (this was necessary to workaround issues with STS and assumed roles) but with the JAR being publicly accessible I wouldn&#039;t expect those credentials to cause problems.&lt;/p&gt;
&lt;p&gt;I can&#039;t easily unset the credentials as they&#039;re baked into the container via an &lt;code&gt;env_file&lt;/code&gt; but I could move this configuration into runtime rather than build time if this is the cause.&lt;/p&gt;
&lt;p&gt;Has anyone else encountered this issue? If so, I&#039;d massively appreciate any suggested workarounds/fixes.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt;: I&#039;ve tried moving the AWS credentials from an &lt;code&gt;env_file&lt;/code&gt; into a read-only volume, which means the &lt;code&gt;AWS_ACCESS_KEY_ID&lt;/code&gt; and &lt;code&gt;AWS_SECRET_ACCESS_KEY&lt;/code&gt; vars are no longer exported at build time. This hasn&#039;t fixed the issue, which leads me to believe it&#039;s not the AWS credentials that are causing the problem. That said, with the AWS credentials in place during build there&#039;s a noticeable delay fetching from both the &lt;code&gt;cognitect-dev-tools&lt;/code&gt; and &lt;code&gt;datomic-cloud&lt;/code&gt; repos.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update 2&lt;/strong&gt;: I&#039;m seeing the same error inside GitHub actions. Not just inside Docker containers…&lt;/p&gt;
</description>
<category>Cloud</category>
<guid isPermaLink="true">https://ask.datomic.com/index.php/546/could-not-find-artifact-com-datomic-ion-jar-0-9-48-in-central</guid>
<pubDate>Thu, 03 Dec 2020 12:29:12 +0000</pubDate>
</item>
</channel>
</rss>