Can't get it work, nothing happens when i start it. Some logs where everything seems normal.

I'm on 6.3.5, and I'm getting this error when I try and start the container:

 

INFO: KVM acceleration enabled
ERROR: AUTO_ATTACH incorrect or undefined. It must be one of [Yy1Nn0]

 

Also getting the following error: 

INFO: KVM acceleration enabled
ERROR: AUTO_ATTACH incorrect or undefined. It must be one of [Yy1Nn0]

Is there a step by step tutorial?

 

On 11/1/2017 at 1:57 PM, Squid said:

I'm surprised that a search for segator through CA didn't pull up the results included xpenology

Anyone make any progress on this?

I'm getting nowhere.

On 12/4/2017 at 10:20 AM, revilo951 said:

I'm on 6.3.5, and I'm getting this error when I try and start the container:

 

INFO: KVM acceleration enabled
ERROR: AUTO_ATTACH incorrect or undefined. It must be one of [Yy1Nn0]

 

@kabloomy posted this, and it seems to work for me

Quote

Add an AUTO_ATTACH variable and set it to Y.

The attached config worked for me. Notice the repository is not as per docker hub, it's:

segator/xpenology:6.1.3-15152

Docker offers an upgraded container that doesn't appear to do anything (?) but attempting to upgrade did reset some settings within the xpenology instance. Does this imply that not all config is stored in the single volume (image)? That might need fixing.

I added a raid group and then a volume (basic, btrfs) from within storage manager.

 

I don't fully understand this (from the segator/xpenology-docker github read.me)

Quote

Mount Docker Host Volumes to Xpenology

To mount Host Path/Docker Volumes to your Xpenology Image you need to load 9p drivers in your xpenology image, follow this tutorial to compile drivers for your specific xpenology version. After have your image with 9p drivers loaded you need to create and script that will executed on every boot in your xpenology, this script will load the drivers and mount your 9p mountpoint, by default this docker image map the path /data to the 9p "hostdata" Example

insmod /volume1/homes/admin/9pnet.ko
insmod /volume1/homes/admin/9pnet_virtio.ko
insmod /volume1/homes/admin/9p.ko
mkdir /volume1/\@unraid
mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144  hostdata /my/host/data

Are the 9P drivers already integrated?

I need an idiot's guide!

if you have shell access run this command.

''docker run --privileged -v /mnt/user/appdata/Xpenology/instance:/image -p 5000:5000 -p 22:5022 segator/xpenology:6.1.3-15152''

Note, you must make the folders match mine. 

Within Xpenology, unzip the files from segators repo, 


And put the synoboot.img in the Xpenology folder also.



This will get you up and running but you cannot edit the docker and make mods, i'm working my way back to try get this running by setting up manually. 

Hopefully now you can work out how to set up manually and show me now

Thanks,




 

 

Edited December 18, 20178 yr by foster182

What's the latest on this docker? Is it being updated/maintained?

Please say yes!

also interested if this is still being updated. Just downloaded it and will have a play later. would be amazing if this is still going

 

@segator any chance you can spare some more time for this?

Hello. Now it works for me, but how is the password and the username to login

Yep stuck on the login screen also

The default login that worked for me is:

username - admin

password - 123456

Hello

 

is there any tutorial how to install this? 

Hi to everyone, sorry to take this topic abandoned, I decided 1 year ago to don't use anymore unraid(No snapshot support, Switched to glusterFS) and I Forgot to answer replies.

Well I see pretty interest in this docker, I don't know the situation of Xpenology right now, it does support latest Synology versions?

Now i'm going 2 weeks to japan, when I return I will try to take time to update and simplify the docker image.

 

 

6 hours ago, segator said:

Hi to everyone, sorry to take this topic abandoned, I decided 1 year ago to don't use anymore unraid(No snapshot support, Switched to glusterFS) and I Forgot to answer replies.

Well I see pretty interest in this docker, I don't know the situation of Xpenology right now, it does support latest Synology versions?

Now i'm going 2 weeks to japan, when I return I will try to take time to update and simplify the docker image.

 

 

Brilliant, thank you segator!

On 9/10/2018 at 10:01 AM, segator said:

Hi to everyone, sorry to take this topic abandoned, I decided 1 year ago to don't use anymore unraid(No snapshot support, Switched to glusterFS) and I Forgot to answer replies.

Well I see pretty interest in this docker, I don't know the situation of Xpenology right now, it does support latest Synology versions?

Now i'm going 2 weeks to japan, when I return I will try to take time to update and simplify the docker image.

 

 

Yes please! 😀

On 9/10/2018 at 10:01 AM, segator said:

Hi to everyone, sorry to take this topic abandoned, I decided 1 year ago to don't use anymore unraid(No snapshot support, Switched to glusterFS) and I Forgot to answer replies.

Well I see pretty interest in this docker, I don't know the situation of Xpenology right now, it does support latest Synology versions?

Now i'm going 2 weeks to japan, when I return I will try to take time to update and simplify the docker image.

 

 

Hey. Have you made any progress with this?

Sorry to nag but I'm really keen to use it!

Any update on this?
Dying to get xpeonolgy up and running on unraid.

Regards,

Sadly this seems to have been abandoned.

I was pretty excited to give this a try depending how the thread was going. Owning a Synology the file manager and app UI is a first-class experience. Good news is this project is on github, and anyone can fork that and make modifications to improve upon it. I see one user has out of the few forks there.

Hi, i just found this and I'm trying to get this run (IntelNuc + LinuxServer + Docker).

My problem is that i get an error while it tries to boot xpenology

 

[    0.024331] general protection fault: 0000 [#1] SMP
[    0.025000] Modules linked in:
[    0.025000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.102 #15152
[    0.025000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
[    0.025000] task: ffff88007c487800 ti: ffff88007c4a4000 task.ti: ffff88007c4a4000
[    0.025000] RIP: 0010:[<ffffffff81881d06>]  [<ffffffff81881d06>] intel_pmu_init+0x2cf/0x7b7
[    0.025000] RSP: 0000:ffff88007c4a7eb0  EFLAGS: 00010202
[    0.025000] RAX: 0000000000000003 RBX: 0000000000000000 RCX: 0000000000000345
[    0.025000] RDX: 0000000000000003 RSI: 0000ffffffffffff RDI: ffffffff81862290
[    0.025000] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000007
[    0.025000] R10: 0000000000000000 R11: ffffffff81862100 R12: 0000000000000000
[    0.025000] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    0.025000] FS:  0000000000000000(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
[    0.025000] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.025000] CR2: ffff880001ab7000 CR3: 000000000180d000 CR4: 00000000003406f0
[    0.025000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.025000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.025000] Stack:
[    0.025000]  ffffffff818810cb ffffffff818810ff ffffffff8102c304 0000000000000000
[    0.025000]  ffffffff818810cb 0000000000000001 0000000000000000 0000000000000000
[    0.025000]  0000000000000000 0000000000000000 ffffffff810003aa ffffffff8191d7f0
[    0.025000] Call Trace:
[    0.025000]  [<ffffffff818810cb>] ? check_bugs+0x28/0x28
[    0.025000]  [<ffffffff818810ff>] ? init_hw_perf_events+0x34/0x506
[    0.025000]  [<ffffffff8102c304>] ? set_memory_x+0x44/0x50
[    0.025000]  [<ffffffff818810cb>] ? check_bugs+0x28/0x28
[    0.025000]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140
[    0.025000]  [<ffffffff8187ad21>] ? kernel_init_freeable+0x95/0x1bb
[    0.025000]  [<ffffffff8149cb60>] ? rest_init+0x70/0x70
[    0.025000]  [<ffffffff8149cb65>] ? kernel_init+0x5/0x180
[    0.025000]  [<ffffffff814aea88>] ? ret_from_fork+0x58/0x90
[    0.025000]  [<ffffffff8149cb60>] ? rest_init+0x70/0x70
[    0.025000] Code: a1 04 fe ff 44 89 0d a2 04 fe ff 89 05 54 05 fe ff 7e 2d 83 e2 1f b8 03 00 00 00 66 b9 45 03 83 fa 02 0f 4e d0 89 15 6a 04 fe ff <0f> 32 48 89 d1 89 c0 48 c1 e1 20 48 09 c1 48 89 0d fd 04 fe ff
[    0.025000] RIP  [<ffffffff81881d06>] intel_pmu_init+0x2cf/0x7b7
[    0.025000]  RSP <ffff88007c4a7eb0>
[    0.025013] ---[ end trace 4b5bc8a6fd37ccbb ]---
[    0.026039] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.026039]

I'm pretty much a Linux Noob so i would be happy if you post potential fixes detailed.

34 minutes ago, Kilian said:

My problem is that i get an error while it tries to boot xpenology

It seems like you aren't talking about Unraid. Does your post have anything to do with our forum? 

This project does still function, but it unfortunately uses the somewhat old DSM version of 6.0.2-8451. I'm hoping to get it running with the latest DSM 6.2.2-24922, but have not quite gotten there yet. In the meantime, for anyone trying to get it up and running, below is the XML template for Unraid that gets it all up and running (I've also attached the file for download).

 

Note: Once you are up and running, you can access the DSM VM via hostIP:5000. Make sure to login with the following default credentials:

user: admin

pass: 123456

 

<?xml version="1.0"?>
<Container version="2">
  <Name>xpenology</Name>
  <Repository>segator/xpenology</Repository>
  <Registry/>
  <Network>bridge</Network>
  <MyIP/>
  <Shell>sh</Shell>
  <Privileged>true</Privileged>
  <Support/>
  <Project/>
  <Overview/>
  <Category/>
  <WebUI/>
  <TemplateURL/>
  <Icon/>
  <ExtraParams/>
  <PostArgs/>
  <CPUset/>
  <DateInstalled>1580171785</DateInstalled>
  <DonateText/>
  <DonateLink/>
  <Description/>
  <Networking>
    <Mode>bridge</Mode>
    <Publish>
      <Port>
        <HostPort>5022</HostPort>
        <ContainerPort>22</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
      <Port>
        <HostPort>5000</HostPort>
        <ContainerPort>5000</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
    </Publish>
  </Networking>
  <Data>
    <Volume>
      <HostDir>/mnt/user/appdata/xpenology/image</HostDir>
      <ContainerDir>/image/</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
  </Data>
  <Environment>
    <Variable>
      <Value>Y</Value>
      <Name>AUTO_ATTACH</Name>
      <Mode/>
    </Variable>
  </Environment>
  <Labels/>
  <Config Name="AUTO_ATTACH" Target="AUTO_ATTACH" Default="" Mode="" Description="This variable is necessary due to the use of segator/kvm. See here: https://github.com/segator/kvm#running" Type="Variable" Display="always" Required="false" Mask="false">Y</Config>
  <Config Name="image" Target="/image/" Default="" Mode="rw" Description="Container Path: /image/" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/xpenology/image</Config>
  <Config Name="SSH Access" Target="22" Default="" Mode="tcp" Description="This allows SSH access to the Synology DSM VM via host port 5022" Type="Port" Display="always" Required="false" Mask="false">5022</Config>
  <Config Name="Web GUI Access" Target="5000" Default="" Mode="tcp" Description="This allows access to the Web GUI of the Synology DSM VM via host port 5000" Type="Port" Display="always" Required="false" Mask="false">5000</Config>
</Container>

 

my-Xpenology.xml

Edited January 28, 20206 yr by swallace

I have been working on this with swallace ^ as well. It seems segator had another version of this project at segator/xpenology-docker rather than segator/xepenology. When trying to run the former, there seems to be a qemu compatibility issue with the latest jun loader/synoboot img. The following error occurs: qemu-system-x86_64: /build/qemu-9fqihN/qemu-2.5+dfsg/block/io.c:853: bdrv_aligned_preadv: Assertion `(bytes & (BDRV_SECTOR_SIZE - 1)) == 0' failed.

 

I have tried passing BDRV_SECTOR_SIZE as a docker env var with a value of 1. This has not resolved it yet. I fear incompatibility, but there could be a simple solution to resolve that error.