Opkg is creating it's lock file under /var/run, which has drwxr-xr-x root-root permissions. Any opkg operation under an unprivilged user will throw: Collected errors: * opkg_lock: Could not create lock file /var/run/opkg.lock: Permission denied. A better place for lock file is /var/run/lock (maps to /run/lock). If writes can be made atomic (via a tmpfile), then reads shouldn't need a lock and an unprivileged user should be able to do any operations than only requires reads. Since any user can create files in /var/run/lock, opkg will need to make sure that the user is root when creating the lock.
*** Bug 8174 has been marked as a duplicate of this bug. ***
/var/run/lock permissions are too open, left lock on /var/run. Commit feb40ec55c07aabe7a925f0338156f71582041a5 removed the need to be root for read-only operations.