| 14 Mar 2023 |
 developer-guy | looking forward to chat about Referrers API | 19:37:15 |
| 25 Mar 2023 |
|  black_blue21 joined the room. | 09:28:52 |
| 29 Apr 2023 |
|  imlostlmao joined the room. | 09:51:57 |
| 2 May 2023 |
|  ctrl-alt-del joined the room. | 11:55:42 |
| 6 May 2023 |
|  @ralph:fx45.in joined the room. | 16:24:42 |
| 16 May 2023 |
|  luffy joined the room. | 00:27:27 |
| 20 May 2023 |
| @ralph:fx45.in left the room. | 22:47:57 |
| 23 Jun 2023 |
|  giuseppe joined the room. | 16:01:00 |
| 24 Jun 2023 |
|  h-vetinari joined the room. | 03:19:52 |
| 26 Oct 2023 |
|  gce108 joined the room. | 16:26:59 |
| 6 Nov 2023 |
|  vbatts changed their display name from vbatts to Marvin. | 19:06:11 |
| vbatts removed their profile picture. | 19:06:45 |
| vbatts changed their display name from Marvin to vbatts. | 19:12:55 |
| vbatts set a profile picture. | 19:14:22 |
| 13 Dec 2023 |
| vbatts changed their profile picture. | 22:06:50 |
| 3 Jan 2024 |
|  @dwitch:matrix.org joined the room. | 16:00:38 |
| @dwitch:matrix.org | is there a way to get an interactive shell in the container, in case of a container build failure? Some oci-hooks trick maybe? https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config.md#posix-platform-hooks does not seem to talk about executing something before a container stops ... | 16:05:56 |
| 29 Jan 2024 |
| @dwitch:matrix.org left the room. | 12:49:02 |
| 3 Feb 2024 |
|  @nam3l33ss:matrix.org joined the room. | 17:23:06 |
| 24 Feb 2024 |
| @nam3l33ss:matrix.org left the room. | 01:28:35 |
| 9 Apr 2024 |
| vbatts left the room. | 22:08:54 |
| 12 Apr 2024 |
|  @colemickens:matrix.org left the room. | 03:59:37 |
| 15 May 2024 |
| @nam3l33ss:matrix.org joined the room. | 18:19:15 |
| @nam3l33ss:matrix.org left the room. | 18:19:42 |
| 31 May 2024 |
| gce108 set a profile picture. | 05:39:59 |
| 7 Aug 2024 |
|  sciurgigus chadolinensis joined the room. | 11:29:52 |
| 23 Aug 2024 |
|  seanomik joined the room. | 19:53:29 |
| seanomik | What should an OCI registry's response be when the client attempts to upload a manifest that already exists? The spec doesn't mention this case, however, the conformance checker seems to attempt to upload the same manifest 4 times in a test. I ended up adding a check to see if the manifest exists and if it does to respond with 201 (CREATED) and that passes the conformance test, just wanted to make sure that's correct. | 20:01:28 |
| 25 Sep 2024 |
|  Hugo Daclon joined the room. | 14:14:50 |
| 9 Oct 2024 |
|  brew93 joined the room. | 11:19:34 |
