Re: [HTCondor-users] Docker logs.

[Dudu Handelman <duduhandelman@xxxxxxxxxxx>]

Thanks Greg. 

I can confirm that docker will have the stdout as well as the output file. Docker will also  have the output when stream_output is set true as well.

Currently Im playing with the max size of docker logs via some docker_extra_args. 

You probably never noticed that because when the container dies the docker stdout dies with it. 

When the job is running you can look at the log using docker logs "container name" 

Will update with the docker arguments when finish testing. 

Thanks

David.

Get Outlook for Android

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Greg Thain via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Monday, December 11, 2023 7:39:15 PM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Cc: Greg Thain <gthain@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Docker logs.

On 12/9/23 10:13, Dudu Handelman wrote:
> Hi All.
> Just want to share some information regarding docker universe.
> Sometimes there are execution points with no disk space on the
> volume/disk that holds the docker folders and the / volume.
> The reason for that is a user job that has a huge stdout.


Hi David:

The stdout for the user job should be redirected onto a disk file often
named _condor_stdout in the $CONDOR_SCRATCH_DIR, if the user has

output = some_file

set in their submit file.  If so, I don't think any of that will go to
the docker logs, and docker won't even see any of that output.  Can you
verify that this is the case?


-greg


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/