# 1.0.0-beta.5 (small bugfix)

**URL:** <https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668>\
**Category:** 📢 Announcements\
**Tags:** beta, i-have-backups, alpha\
**Created:** [June 9, 2021, 7:23am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668 "2021-06-09T07:23:18Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\
**Post date:** [June 9, 2021, 7:23am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/1 "2021-06-09T07:23:18Z")

</div>

Only one bugfix from [beta.4](https://forum.photostructure.com/t/1-0-0-beta-4-is-ready/647):

🐛 [Fixed asset info panel dropdowns](https://forum.photostructure.com/t/1-0-0-beta-4-is-ready/647/10)

Installation instructions are here:

> [@Version 1.0.0-beta.3 reporting for duty](https://forum.photostructure.com/t/version-1-0-0-beta-3-reporting-for-duty/615):
>
> Beta? What’s that? Remember: beta builds should be considered experimental and may be unstable, although this one’s looking like it might be promoted to v1.0.0. [Read more about alpha, beta, and stable releases here.](https://forum.photostructure.com/t/alpha-beta-stable-and-latest-what-should-you-use/274)Installation instructions PhotoStructure for Desktop users if you’re on an alpha or beta build already, just select “check for updates” and PhotoStructure should upgrade to -beta.3 automatically. If not, download a new installer here: [https://photostructure.com/install/?beta](https://photostructure.com/install/?beta) …

Note that I’ll be offline for the next several days:

> [@Where's Matthew? (8 June 2021)](https://forum.photostructure.com/t/matthews-out-of-the-office-until-next-week/666):
>
> I’ll be away from my desk until next week. Feel free to continue to post questions, bugs, and suggestions: I’ll get to them starting next Monday. Cheers!

---

<div class="post-metadata">

**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\
**Post date:** [June 9, 2021, 7:32am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/2 "2021-06-09T07:32:43Z")

</div>

Guh, at least for my local docker-powered library, the bug isn’t fixed (I’d reproduced it on my own library running node, changed the dropdown slot rendering, rebuilt, and it worked, _honest_, so… there’s something else going on here). I’ll fix this next week.

---

<div class="post-metadata">

**Author:** ![adept](https://forum.photostructure.com/user_avatar/forum.photostructure.com/adept/32/486_2.png) [@adept](https://forum.photostructure.com/u/adept)\
**Post date:** [June 10, 2021, 9:22pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/3 "2021-06-10T21:22:19Z")

</div>

Seems like another issue with beta.5 docker image:

```auto
2021-06-10T21:12:55.603Z sync-9427 warn WorkQueue(afq:psfile://QGNKQQA5y/) handleError() { qi:
   { '$ctor': 'stats.QueueItem',
     contents:
      '/var/photos/archive/XXXXXXXX/IMGP4294.JPG',
     id: 63687,
     queueId: 15,
     type: 'image' },
  err:
   { name: 'Error',
     stack:
      [ 'Error: invalid file /var/photos/archive/XXXXXXXX/IMGP4294.JPG: code ENOENT: spawn /ps/app/tools/linux-x64/jpegtran/jpegtran ENOENT⁶³²',
        ' at Object.t.asError (/ps/app/bin/sync.js:9:566594)',
        ' at F.processItem (/ps/app/bin/sync.js:9:747481)',
        ' at runMicrotasks (<anonymous>)',
        ' at runNextTicks (node:internal/process/task_queues:61:5)',
        ' at processTimers (node:internal/timers:497:9)' ] } }

```

I’ve checked manually, and while the file is there, it refuses to run, and image does not have dev tools like ldd lying around to try and figure out what is the cause of this

---

<div class="post-metadata">

**Author:** ![adept](https://forum.photostructure.com/user_avatar/forum.photostructure.com/adept/32/486_2.png) [@adept](https://forum.photostructure.com/u/adept)\
**Post date:** [June 10, 2021, 9:23pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/4 "2021-06-10T21:23:33Z")

</div>

Sorry, posted to the wrong thread: [1.0.0-beta.4 is ready! - #16 by adept](https://forum.photostructure.com/t/1-0-0-beta-4-is-ready/647/16) and two messages before that

---

<div class="post-metadata">

**Author:** ![adept](https://forum.photostructure.com/user_avatar/forum.photostructure.com/adept/32/486_2.png) [@adept](https://forum.photostructure.com/u/adept)\
**Post date:** [June 10, 2021, 9:27pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/5 "2021-06-10T21:27:36Z")

</div>

Ok, looks like /ps/app/tools/linux-x64/jpegtran/jpegtran is built with gnu libc:

```auto
# strings jpegtran | grep ld
/lib64/ld-linux-x86-64.so.2

```

I see only musl dynamic linker in the image, and not /lib64 at all:

```auto
# ls -l /lib/ld-musl-x86_64.so.1 
-rwxr-xr-x 1 root root 604736 Jun 7 09:40 /lib/ld-musl-x86_64.so.1

```

Unsurprisingly, musl linker cant dynlink jpegtran:

```auto
# /lib/ld-musl-x86_64.so.1 jpegtran 
Error relocating jpegtran: __fprintf_chk: symbol not found
Error relocating jpegtran: __sprintf_chk: symbol not found

```

Looks like same issue is present in beta.4 image as well

In beta.3, jpegtran is located in /usr/bin/jpegtran and works perfectly fine.

My host (though i suspect that it is not really important apart from host os being linux):  
Linux 4.4.59+ #23824 SMP PREEMPT Fri Oct 26 18:34:30 CST 2018 x86\_64 GNU/Linux

---

<div class="post-metadata">

**Author:** ![venza](https://forum.photostructure.com/user_avatar/forum.photostructure.com/venza/32/432_2.png) [@venza](https://forum.photostructure.com/u/venza)\
**Post date:** [June 11, 2021, 7:38am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/6 "2021-06-11T07:38:23Z")

</div>

I’m hitting the same problem, thanks for the analysis.

---

<div class="post-metadata">

**Author:** ![avdp](https://forum.photostructure.com/user_avatar/forum.photostructure.com/avdp/32/557_2.png) [@avdp](https://forum.photostructure.com/u/avdp)\
**Post date:** [June 11, 2021, 7:35pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/7 "2021-06-11T19:35:51Z")

</div>

Yes, @mrm suspected that was the problem

> [@BUG? - Too few pictures imported](https://forum.photostructure.com/t/bug-too-few-pictures-imported/672/9):
>
> beta.2 works! beta.3,4,5 don’t.

---

<div class="post-metadata">

**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\
**Post date:** [June 14, 2021, 8:25pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/8 "2021-06-14T20:25:41Z")

</div>

@adept @venza @avdp thanks for the analysis! Turns out my `.dockerignore` lost the `tools` line, so this was literally a one-liner fix. I shipped it with beta.6.

---

<div class="post-metadata">

**Author:** ![venza](https://forum.photostructure.com/user_avatar/forum.photostructure.com/venza/32/432_2.png) [@venza](https://forum.photostructure.com/u/venza)\
**Post date:** [June 15, 2021, 7:01am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/9 "2021-06-15T07:01:28Z")

</div>

Hello,  
With beta.7 the import process works with the Docker image, but only if the volume is read-write.  
If I add the “:ro” at the end of the -v docker option, PhotoStructure will run the import without any obvious error, but there are no thumbnails and nothing is imported.

Note: my volume is actually an NFS volume mounted in /mnt/photo on the host, in Docker I add a subdirectory as a volume for the container (-\> /mnt/photo/Root)

---

<div class="post-metadata">

**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\
**Post date:** [June 15, 2021, 11:47pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/10 "2021-06-15T23:47:37Z")

</div>

> [@venza](#):
>
> add the “:ro” at the end of the -v docker option

Is this adding `:ro` to a bind mount that you want to import? (`/ps/library` needs to be read/write, of course).

I can’t think why scanning the directory in readonly mode would make the import work. If you want to [share logs](https://photostructure.com/faq/error-reports/#how-to-manually-send-your-logs), I can take a look at what’s going on.

---

<div class="post-metadata">

**Author:** ![venza](https://forum.photostructure.com/user_avatar/forum.photostructure.com/venza/32/432_2.png) [@venza](https://forum.photostructure.com/u/venza)\
**Post date:** [June 16, 2021, 4:49am UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/11 "2021-06-16T04:49:21Z")

</div>

I’m sorry, I was not clear. By volume I meant the volume where I store my pictures, not the library.

```auto
docker run \
  --name photostructure \
  --detach \
  --restart on-failure \
  --stop-timeout 120 \
  --publish 1787:1787 \
  -e TZ="$(cat /etc/timezone)" \
  -v "$PSLIBRARY":/ps/library \
  -v "$PSTMP":/ps/tmp \
  -v "$PSCONFIG":/ps/config \
  -v "$PSLOGS":/ps/logs \
  -e PS_LOG_LEVEL=info \
  -e PS_TAIL_LOGS=1 \
  -v "/mnt/photo/Root:/pictures" # <-- ADD :ro TO THIS LINE AND THE IMPORT FAILS \
  photostructure/server:beta

```

I no longer have the logs, btw the button at the end of the menu “Send us your recent logs” for me fails consistently.

Best,  
Daniele

---

<div class="post-metadata">

**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\
**Post date:** [June 16, 2021, 7:06pm UTC](https://forum.photostructure.com/t/1-0-0-beta-5-small-bugfix/668/12 "2021-06-16T19:06:09Z")

</div>

> [@venza](#):
>
> “Send us your recent logs” for me fails consistently.

Sorry about that! My error reporting service changed their API which means the error reporting service is now a source for errors. 💃