mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de,
	"Rajkumar Athimoolam (RBEI/ECG-EP3)" <Rajkumar.A2@in.bosch.com>
Subject: Re: [ptxdist] ./p images failure inside a docker container
Date: Fri, 2 Nov 2018 15:29:23 +0100	[thread overview]
Message-ID: <c9eb4d3f-90f5-3fa7-79a4-275da88cc4bf@pengutronix.de> (raw)
In-Reply-To: <2bf2593ef41948d49edfd129a55caa43@in.bosch.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 934 bytes --]

On 11/02/2018 01:03 PM, Rajkumar Athimoolam (RBEI/ECG-EP3) wrote:
> Hi,
>  
> I have created a docker image with ptxdist and oselas toolchain and
> trying to generate ubifs image for our project.
> But the image generation fails while generating the signed image with
> below output
>  
> /Signing (debug - prepare step)
> '/tmp/ptxdist.hjTgt3/genimage.FOmRZ2/data' this may take some
> time...ioctl() failed/
> /errno: Inappropriate ioctl for device (25)/
>  
> Am I am missing something inside docker container? Because usually it
> works fine outside the docker container

What's the filesystem of /tmp inside your container?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-11-02 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 12:03 Rajkumar Athimoolam (RBEI/ECG-EP3)
2018-11-02 14:29 ` Marc Kleine-Budde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c9eb4d3f-90f5-3fa7-79a4-275da88cc4bf@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Rajkumar.A2@in.bosch.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox