Received: from wolfsden.cz (wolfsden.cz [37.205.8.62]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id A9D28782B92 for <~alpine/users@lists.alpinelinux.org>; Sun, 26 Apr 2020 00:27:07 +0000 (UTC) Received: by wolfsden.cz (Postfix, from userid 110) id 7847829BD9E; Sun, 26 Apr 2020 00:27:06 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on wolfsden X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_ALL,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from localhost (unknown [128.0.188.242]) by wolfsden.cz (Postfix) with ESMTPSA id D5F4629BAB5; Sun, 26 Apr 2020 00:27:05 +0000 (UTC) Date: Sun, 26 Apr 2020 02:27:04 +0200 From: Wolf To: spam@ipik.org Cc: ~alpine/users@lists.alpinelinux.org Subject: Re: struggling with apk in unattended session Message-ID: <20200426002704.azrjjvoqhyhcsx4g@wolfsden.cz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="v3hi2roepl5dwv24" Content-Disposition: inline In-Reply-To: --v3hi2roepl5dwv24 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, On 2020-04-24 16:29:39 +0200, spam@ipik.org wrote: > I=E2=80=99m trying to run apk command in an embedded system under no end-= user > console/ssh interaction. > The set of scripts running the apk command works great when launched > from ssh session (produces output and log), or for instance, if it is > gated by an acpid input device (thus under root) > However, when launched by another process ( owned by user =E2=80=9Cjoe=E2= =80=9D, who > has sudo rights on script), apk command seems to block: other preceding > commands do produce expected results and logs, but it stumbles on apk. >=20 > Are there any special consideration to take care about with apk in such > scenario? > Thanks for any tip! I'm not aware of anything specific and to the best of my (limited) knowledge I would expect your snippets to work. Any chance you could put together steps to reproduce this in for example alpine docker container? Ideally starting from clean docker run alpine, step by step. That would probably help with figuring out the issue quite a bit. W. --=20 There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. --v3hi2roepl5dwv24 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7BIrb0FxyZaks1p7hTP5S2N55TgFAl6k1VgACgkQhTP5S2N5 5TjsIA/+IBJFC0RzEoIvfE5nDZG5JPRHIQFzOi5GatGdeGVcDljehSuYBIX086Y5 cLqup55EBMidOpn6MTk9UhuiPOXGvurzXPrVVi3KSAcwTOgtjqJLeddkI4hN8oed lVk2dlsGkte6CR9QbcuRpnAVZfFdx0KXGkHoTuoO+MbwArw00W/fkl9mGfOt5/KX M1VyVhcqvQGHaCguXVqF4maDyd+pimtEQuvenoYVFuwiM4+CRfXQN+5uD3ozDW2o sCnWP258kYb+rRY5q0FATJJZpEXRb+YXE7DmcrJHK8wliXOHsMl+CbucqakfcoB+ bUVUdwzFXDzn+EmbwZ52IxkxRqRy59PTFDjXkP+6GQHgGBbkovRUX/LmjohExw7O n17XyrLjV+LrpifppAValAOKFq+fb9n7RgKCg2puZXMlSvHjV1PPYzogk5xXp/1t N8zNjpBzSJwUhD57BAlP4bFetMPzVQDrYWqFjPprB2J2viH4KLzOlN63TfZ43AOL oxW2efmyQrtLyIrZtbe80wd848nz6v4o7DJqUM0fm+iSQmCWHFgtY6kfOxOPxiwc UeJhMavsgTlo8nQdcaeEw66AM83z0mnD6V+J914+mm0cFdDe3UpsAMg7eFLhLZ7p R3QZdtmM7xHDCvuXFEy0EAZaZXDfj+7jaVG49bM61lC8ArJQj8Q= =gJql -----END PGP SIGNATURE----- --v3hi2roepl5dwv24--