-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve ways to install & documentation for it #2250
Comments
@h-vetinari Have you gotten access to a newer version of podman? |
Unfortunately, no. It would be nice to have install-procedures that boil down to a |
I am not sure why on a RHEL machine you are having a hard time getting access to podman? It should be in your extras channel. Which is the same location that you got docker from. On Centos packages have been made available, but I am not sure where. @lsm5 Where are the packages from Centos. |
@rhatdan, I have podman on the RHEL machine, but not the latest version, much less master. If you want me to file bug reports against v.0.11, I can. See OP:
Side note: the productive RHEL machine is not under my full control - particularly, I can't just download stuff. On other machines I can test (e.g. CentOS), I have more liberty. |
@lsm5 Do we have a newer version of podman for RHEL7.6 yet? |
I have had a look at packaging podman for Debian, but from my point of view, the current Ubuntu packages made it way too complicated. Since I want to run podman rootless inside the user podman and don't others be abler to run it, building the whole stack is pretty straight forward. Though there are some cmd-parameters missing in podman, which pointto slirp4netns binary for example, but this can be hacked by path variables. I'll release my code in the next days. Need to finish something for University first. |
@tobwen @lsm5 @rhatdan |
Yes These should be released on the next release of extras. |
@h-vetinari some prototypes... I'm using the ugly bash script to keep traffic to the GIT servers low. Sure, you can just wipe the GO-directory and build from scratch. This works for me on rootless. Only fuse3 installations needs root of course. HOWTO: backport fuse3 for Debian Stretchhttps://gist.github.com/tobwen/c1fc1512458ce272aee2410e36cf1e21 HOWTO: install podman and dependencies rootlesshttps://gist.github.com/tobwen/25a010d3b90a6491e5646c0e77163557 I'll add some examples for config files to podman soon. Right now, it won't find the other libraries and tools without making them available in path, change the path variable or add command-line parameters. |
@lsm5 ^^ |
Pleasantly surprised to see that This should however still be updated in @rhatdan @lsm5 |
On Thu, Mar 28, 2019 at 05:48:02AM -0700, h-vetinari wrote:
Pleasantly surprised to see that [`install.md`](https://github.com/containers/libpod/blob/master/install.md#ubuntu) now has a ppa for ubuntu. Bit surprised that the installed version is `1.2-dev` (as opposed to last stable), but that's good for filing bugs at least. ;-)
1.2-dev because master branch is built nightly via Travis.
Snap packages are planned, but that might take a while.
This should however still be updated in [`docs/tutorials/podman_tutorial.md`](https://github.com/containers/libpod/blob/master/docs/tutorials/podman_tutorial.md).
@rhatdan @lsm5
Any news when a newer podman will hit 7.6 EPEL?
Never on EPEL, unless you mean CentOS Extras or Virt SIG?
Virt SIG I'll update soon, though CentOS Extras might take a while.
…
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#2250 (comment)
--
Lokesh
IRC, GitHub: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5
|
@lsm5 Thanks for taking the time to answer
OK, cool
Sorry if the naming was wrong, I meant RHEL 7.6 extras. Point being, when can I install something newer than podman 0.11.1 on a RHEL 7.6 machine? |
On Thu, Mar 28, 2019 at 06:06:43AM -0700, h-vetinari wrote:
@lsm5 Thanks for taking the time to answer
> 1.2-dev because master branch is built nightly via Travis.
OK, cool
> > Any news when a newer podman will hit 7.6 EPEL?
> Never on EPEL, unless you mean CentOS Extras or Virt SIG?
Sorry if the naming was wrong, I meant RHEL 7.6 [extras](https://access.redhat.com/solutions/3418891). Point being, when can I install something newer than podman 0.11.1 on a RHEL 7.6 machine?
Looks like 0.12.1.2 was shipped about 2 months ago. Aren't you seeing that one?
Something newer than that will take a few weeks more I guess.
--
Lokesh
IRC, GitHub: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5
|
@h-vetinari @lsm5 What is the latest on this issue? |
@rhatdan
Regarding other points in the discussion, I'd need to have an update of podman/buildah in the RHEL 7.6 extras channel as soon as possible, but before I'd really need for containers/buildah#1456 and #2887 to be fixed first. Can open a separate issue for this if you want. |
@rhatdan Would you accept a PR to merge the installation instructions from |
Why *.rst and not *.md? |
Because I typed the filename from memory and got the extension wrong... Sorry. |
@h-vetinari Yes we would love a PR. |
@h-vetinari no worries on the file name. Personally, I'd like to see the install instructions be their own page with a link from the tutorial. |
I've been trying to use
podman
- forced by RH policy of not upgrading thedocker
runtime in RHEL anymore, and so far it has been far from a drop-in replacement.Since the last release I have access to within the newest RHEL7.6 is podman 0.11.1, I can't even start filing all the bugs I'm encountering, because - who knows - maybe they're fixed on master already.
So off I go trying to install this somewhere I fully control. This leads me to this issue:
[apt-get|yum|...] install podman
), there should be clear documentation for getting the latest version.podman build
(with a cryptic error), almost certainly because I'll need to install buildah..deb
package?So far, the experience has been incredibly frustrating (simple things like tagging don't work, caching is hit-and-miss [+ some weird interactions with keywords],
podman build
andbuildah bud
don't share cache,--target
is not supported, etc. etc.).Although I'm hoping that some of these bug fixes will still make it into RHEL8.0 (so that I can maybe use it later this year), current status is that I'll have to go back to the lack of features (but much greater stability) of
docker 1.13
.The text was updated successfully, but these errors were encountered: