Hi David,
No problem. As the mailing list doesn't accept attachment, feel free to
send to me directly.
Thanks
Regards
JB
On 30/10/2019 01:19, David Leangen wrote:
Thanks JB,
I’ll try to comb through the lists to figure out precisely what you mean by “a
simple test”. Apologies for my ignorance… 😬
I’ll get back to you soon.
Cheers,
=David
On Oct 30, 2019, at 2:10, Jean-Baptiste Onofré <[email protected]> wrote:
Hi,
the easy path would be the features XML with a zip of your resources repository.
A simple test should be enough.
Thanks a lot !
Regards
JB
On 29/10/2019 11:13, David Leangen wrote:
Hi JB,
Sure! What would be the best way of doing that?
I could give you a reference to my docker image, config changes, and repo and
you run it?
Or give you access to a running server instance?
Or something else?
Cheers,
=David
On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré <[email protected]> wrote:
Hi David,
do you think you can have a simple test case you can send to me ?
It would help to identify the issues between 4.2.0 and 4.2.1.
Thanks,
Regards
JB
On 29/10/2019 09:29, David Leangen wrote:
4.2.1 was a no-go. The same problem occurred as with 4.2.7.
So it appears that the problematic change got introduced sometime between 4.2.0
and 4.2.1.
For now, I will try to get my system up and running in 4.2.0 if I can figure
out the resolution problems, but it would still be great to figure out why
4.2.7 won’t start up…
Cheers,
=David
On Oct 29, 2019, at 17:15, David Leangen <[email protected]
<mailto:[email protected]>> wrote:
Hi,
FYI it looks like 4.2.0 worked. I am having trouble with resolution of my
bundles now, but at least the problem I was seeing in 4.2.7 is not there.
I will give it a try with 4.2.1 next.
Cheers,
=David
On Oct 28, 2019, at 20:14, David Leangen <[email protected]
<mailto:[email protected]>> wrote:
The owner of the file (as well as the directory) is karaf.karaf.
From /etc/passwd:
karaf:x:1001:1001::/home/karaf:/bin/bash
From /etc/group:
karaf:x:1001:
The owner of the docker process in which karaf is running is root.
So I don’t think it’s a permissions problem.
The etc directory is mounted as a volume. It seems to be working fine (i.e.
files can be changed both within the container and on the host).
Cheers,
=David
On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>> wrote:
Hmmm,
does the user running Karaf has permission to read the file/folder ?
Regards
JB
On 28/10/2019 08:11, David Leangen wrote:
You amaze me! How are you so fast?
Anyway…
Again you’ll have to excuse my ignorance, but…
[root@deimos features]# pwd
/home/karaf/features
[root@deimos features]# ls
01-enroute.xml 03-base.xml 05-platform.xml 07-ddd.xml 09-app.xml integral.xml
ws.xml
02-patches.xml 04-bucketz.xml 06-web.xml 08-application.xml
10-installation.xml licensing.xml
[root@deimos features]#
Then:
karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
Adding feature url file:/home/karaf/features/01-enroute.xml
Error executing command: /home/karaf/features/01-enroute.xml (No such file or
directory) : file:/home/karaf/features/01-enroute.xml
karaf@root()>
Cheers,
=David
On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]><mailto:[email protected]>> wrote:
Hi,
You can do:
feature:repo-add file:/path/to/your/features.xml
Then
feature:install -v -t enroute
Regards
JB
