Proxmox Virtual Environment 9.1 available!

[t.lamprecht]

Plus I noticed that console is not available for such containers. Is it a bug or a feature?

Currently by design, it basically shows the stdout/in of the main init process, but not buffered.
We want to explore making that output a ringbuffer, that saves the last few KiB of output and provides that as read-only view, and additionally providing shell access to the CT insides as options to improve that experience.

 

[nautilus7]

This ^^
Plus I noticed that console is not available for such containers. Is it a bug or a feature?
Finally, I cannot configure such container with slaac ipv6.

net0: SLAAC is not supported for host-managed network configuration. (500)

 

[PigLover]

Currently by design, it basically shows the stdout/in of the main init process, but not buffered.
We want to explore making that output a ringbuffer, that saves the last few KiB of output and provides that as read-only view, and additionally providing shell access to the CT insides as options to improve that experience.

I think having a buffer of stdout is a great idea - especially if the user can specify the buffer size and there is a way to allow it to be read/processed by other containers or VMs for log review.

However - you still need some form of console access (similar to "docker exec") for troubleshooting and managing your containers. It doesn't have to be complex but it is necessary.

 

[t.lamprecht]

However - you still need some form of console access (similar to "docker exec") for troubleshooting and managing your containers. It doesn't have to be complex but it is necessary.

Yes, that's what I meant with:

additionally providing shell access to the CT insides as options to improve that experience.

 

[t.lamprecht]

net0: SLAAC is not supported for host-managed network configuration. (500)

Yeah, that's by design for now, but feel encouraged to open an enhancement request over at https://bugzilla.proxmox.com/ to keep track of this.

 

[Zamana]

Hello!

I did create a Jackett container (https://hub.docker.com/r/linuxserver/jackett) and it is up and running!

No I'm trying to create a bazarr container (https://hub.docker.com/r/linuxserver/bazarr) and I'm receiving this error:

Detected OCI archive
TASK ERROR: unable to create CT 6767 - Invalid argument

I tried to change some parameters but nothing has changed.

So... which "argument" is this?

Is there any log somewhere?

Thanks.
Regards.