rohityadavcloud commented on PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#issuecomment-1665862763
If there are any new changes @kiranchavala pl submit as separate PR cc
@harikrishna-patnala
--
This is an automated message from the Apache Git Service.
To
rohityadavcloud merged PR #53:
URL: https://github.com/apache/cloudstack-terraform-provider/pull/53
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
davidjumani commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1234155688
##
README.md:
##
@@ -48,9 +48,14 @@ $ make build
$ ls $GOPATH/bin/terraform-provider-cloudstack
```
Once the build is ready, you have to copy
davidjumani commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1234155294
##
README.md:
##
@@ -48,9 +48,14 @@ $ make build
$ ls $GOPATH/bin/terraform-provider-cloudstack
```
Once the build is ready, you have to copy
kiranchavala commented on PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#issuecomment-1521616587
@rohityadavcloud @davidjumani @shwstppr
Could you please review this
--
This is an automated message from the Apache Git Service.
To respond to the
harikrishna-patnala commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1116903349
##
README.md:
##
@@ -91,16 +105,16 @@ In order for all the tests to pass, you will need to
create a new (empty) projec
$ make testacc
kiranchavala commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1116867776
##
README.md:
##
@@ -91,16 +105,16 @@ In order for all the tests to pass, you will need to
create a new (empty) projec
$ make testacc
```
kiranchavala commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1116867776
##
README.md:
##
@@ -91,16 +105,16 @@ In order for all the tests to pass, you will need to
create a new (empty) projec
$ make testacc
```
harikrishna-patnala commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1116841008
##
README.md:
##
@@ -91,16 +105,16 @@ In order for all the tests to pass, you will need to
create a new (empty) projec
$ make testacc
harikrishna-patnala commented on code in PR #53:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/53#discussion_r1116841008
##
README.md:
##
@@ -91,16 +105,16 @@ In order for all the tests to pass, you will need to
create a new (empty) projec
$ make testacc
Op 07-09-2022 om 09:34 schreef Nux:
Wido,
I've just run the UI standalone on a separate machine the other day, but
not on docker.
What I did was to install cloudstack-ui rpm package, then serve it like
a normal site, but proxy /client to mgmt-server:8000 like described here:
https
Unless you're adamant on _building_ the UI, then you could create a
docker container with the rpm/deb instead, if that helps.
---
Nux
www.nux.ro
On 2022-09-07 08:34, Nux wrote:
Wido,
I've just run the UI standalone on a separate machine the other day,
but not on docker.
What I did
Wido,
I've just run the UI standalone on a separate machine the other day, but
not on docker.
What I did was to install cloudstack-ui rpm package, then serve it like
a normal site, but proxy /client to mgmt-server:8000 like described
here:
https://github.com/apache/cloudstack/tree/main/ui
Hi,
Anybody there running the UI outside the Management Server in a Docker
container like described here?
https://github.com/apache/cloudstack/tree/main/ui
I have a use-case for this we would like to investigate, but the build
currently fails [0].
Is this still relevant and supported
‘Official’ CloudStack docker images should be published via the Apache org
account. They’ll have all the payment stuff sorted
Kind Regards
Paul Angus
From: Sina Kashipazha
Sent: Monday, November 22, 2021 10:25 AM
To: Wei ZHOU
Cc: dev@cloudstack.apache.org
Subject
Hey again,
I've checked that, Docker CE and Docker CLI are still free ;)
Kind regards,
Sina
‐‐‐ Original Message ‐‐‐
On Monday, November 22nd, 2021 at 11:05, Sina Kashipazha
wrote:
> Hey Wei,
>
> I couldn't find anything on their website regarding the CLI usage.
heads up. It seems the new policy is applicable for Docker
> Desktop only. We can still use Docker CLI for free, Right ?
>
> -Wei
>
> On Mon, 22 Nov 2021 at 10:30, Sina Kashipazha
> wrote:
>
> > Hey,
> >
> > BTW, it is worth mentioning that Docker
Hi Sina,
Thanks for the heads up. It seems the new policy is applicable for Docker
Desktop only. We can still use Docker CLI for free, Right ?
-Wei
On Mon, 22 Nov 2021 at 10:30, Sina Kashipazha
wrote:
> Hey,
>
> BTW, it is worth mentioning that Docker has changed its subscription
Hey,
BTW, it is worth mentioning that Docker has changed its subscription policy. If
you are a company with more than $10 million in annual revenue, you have to
upgrade to the business account. I quoted the following paragraph from their
FAQ. I'm not clear if it has any effects on open source
Agrees.
There are many users using docker, but for different goals. Depends on
requirements, the solutions are also different.
1. What OS ?
2. Use docker for packaging , demo or testing changes ?
3. Are packages ready ? official releases, nightly build or need to build
packages from source code
Hello Marcus
I was actively using docker files to deploy my own changes in kubernetes and
also to deploy multiple pods with different versions but I havent played out
with reducing the image size. I made changes to docker files to just build the
components I changed rather than building entire
a user defined one)
>
> It was based on the premise of as few layers as possible, all as small as
> possible. (and it was for 4.14)
>
> https://github.com/PaulAngus/docker-simulator
>
> caveat emptor - its not finished and there are some lines that were just
> for debuggi
. (and it was for 4.14)
https://github.com/PaulAngus/docker-simulator
caveat emptor - its not finished and there are some lines that were just for
debugging in there
There may be some ideas that are worth cherry-picking from in there.
Kind Regards
Paul Angus
-Original Message-
From
Cool, we are on the same page there. I think I have something working to
share soon.
I did also consider just installing RPMs or DEBs into a Docker image like a
standard install, which might be a good pattern for official releases so we
can rely on the same package dependency resolution for all
ver played with the Dockerfile you've mentioned.
> > I need to double-check on it, but I would like to see CloudStack Docker
> > images "officially" supported in order to deploy management nodes
> > (especially for development and testing) and build packages.
> >
&g
and then
maybe deprecating and removing the old unused ones over time.
On Wednesday, November 17, 2021, Sina Kashipazha
wrote:
> Hey Marcus,
>
> We use docker to build cloudstack packages when we want to build
> cloudstack for the different target OS. That is our only use case, which
&g
like to see CloudStack Docker
> images "officially" supported in order to deploy management nodes
> (especially for development and testing) and build packages.
>
> In terms of using Docker to build CloudStack packages, I have used a lot of
> the repository from Khosrow Moossa
Hi Marcus,
Sometimes I use the docker images to build a simulator environment. the
docker images are built from tools/docker/Dockerfile
I have uploaded some images to
https://hub.docker.com/repository/docker/ustcweizhou/cloudstack-simulator
The docker images are very large indeed (1.78 GB after
like
/proc/meminfo and scripts with bash 4 arrays. Maybe some of that could be
fixed but I think building in Docker is a common and reasonable pattern too.
On Wednesday, November 17, 2021, Rohit Yadav
wrote:
> Hi Marcus,
>
> I'm not sure about others, I don't use docker so can't reply.
&
Hey Marcus,
We use docker to build cloudstack packages when we want to build cloudstack for
the different target OS. That is our only use case, which happens once in a
blue moon :)
Kind regards,
Sina
‐‐‐ Original Message ‐‐‐
On Tuesday, November 16th, 2021 at 22:30, Marcus wrote
Hi Marcus,
I have never played with the Dockerfile you've mentioned.
I need to double-check on it, but I would like to see CloudStack Docker
images "officially" supported in order to deploy management nodes
(especially for development and testing) and build packages.
In terms of us
Hi Marcus,
I'm not sure about others, I don't use docker so can't reply.
I like to build/develop/run/debug management server process outside of docker;
just using mvn with an IDE for code-development and for attaching remote socket
for breakpoints and debugging. I use mbx to create dev boxes
I take the silence to perhaps mean that nobody is actively using the Docker
image tooling, but maybe the conference was just too much of a distraction
last week :-)
Mainly I'm just wondering if I should be trying to improve the old stuff,
or leaving it be and adding a new Dockerfile. The marvin
Hi all, I've been familiarizing myself with the Docker image tooling in
CloudStack, and I have a few questions. I've been playing with a
multi-stage build that shrinks the image from ~4Gi to ~800Mi, packages just
the jar, some UI, and a JDK thinking that it might be more usable.
1
rhtyd merged pull request #916:
URL: https://github.com/apache/cloudstack-primate/pull/916
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
wido opened a new pull request #916:
URL: https://github.com/apache/cloudstack-primate/pull/916
By switching to this directory we can use relative paths regardless
of how people execute the script.
cd tools
./docker.sh
OR
./tools/docker.sh
OR
rhtyd merged pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-708387715
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/802
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-708381369
@Pearl1594 a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
Pearl1594 commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-708380954
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
davidjumani commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r504546201
##
File path: src/store/modules/user.js
##
@@ -274,6 +274,16 @@ const user = {
reject(error)
})
})
+},
+
davidjumani commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r504546201
##
File path: src/store/modules/user.js
##
@@ -274,6 +274,16 @@ const user = {
reject(error)
})
})
+},
+
davidjumani commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r504546201
##
File path: src/store/modules/user.js
##
@@ -274,6 +274,16 @@ const user = {
reject(error)
})
})
+},
+
Pearl1594 commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r504543884
##
File path: src/components/view/ListView.vue
##
@@ -439,7 +439,7 @@ export default {
value: this.editableValue
}).then(json
rhtyd commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r504542379
##
File path: src/components/view/ListView.vue
##
@@ -439,7 +439,7 @@ export default {
value: this.editableValue
}).then(json => {
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707705834
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/802
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707701365
@Pearl1594 a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
Pearl1594 commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707700745
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
shwstppr commented on a change in pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802#discussion_r503890497
##
File path: src/views/compute/CreateKubernetesCluster.vue
##
@@ -307,6 +366,7 @@ export default {
},
methods: {
fetchData () {
+
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707089102
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/802
blueorangutan commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707084780
@Pearl1594 a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
Pearl1594 commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707084264
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
davidjumani commented on pull request #802:
URL:
https://github.com/apache/cloudstack-primate/pull/802#issuecomment-707058475
Fixes https://github.com/apache/cloudstack-primate/issues/801
This is an automated message from
Pearl1594 opened a new pull request #802:
URL: https://github.com/apache/cloudstack-primate/pull/802
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
rhtyd commented on pull request #626:
URL:
https://github.com/apache/cloudstack-primate/pull/626#issuecomment-681709981
LGTM, thanks @onitake
This is an automated message from the Apache Git Service.
To respond to the
rhtyd merged pull request #626:
URL: https://github.com/apache/cloudstack-primate/pull/626
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
j-porsche commented on pull request #626:
URL:
https://github.com/apache/cloudstack-primate/pull/626#issuecomment-681696288
@svenvogel We tested it and it works fine.
This is an automated message from the Apache Git
on a Debian buster base system with the distribution's
Docker version and on CentOS 8 with Podman.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
synergiator commented on issue #57:
URL:
https://github.com/apache/cloudstack-cloudmonkey/issues/57#issuecomment-626289068
@rhtyd hurray! Thank you.
Though it would be good also to have a tag with explicit version number.
rhtyd commented on issue #57:
URL:
https://github.com/apache/cloudstack-cloudmonkey/issues/57#issuecomment-626110138
@synergiator https://hub.docker.com/r/apache/cloudstack-cloudmonkey/builds
is available now
This is an
Caused by: java.net.SocketException: Protocol family unavailable
This is a common Java issue when trying to containerize, I believe you can
search for it and find a generic answer. Basically has to do with whether
Java is trying to use IPv4 or IPv6 and what your Docker solution supports.
If I
Hi ALL
I'm trying to encapsulate cloudstack 4.11 into docker. After build is
successful, cloudstack-management cannot function properly.
Can someone help me? Thank you very much.
Dockerfile:
https://github.com/apache/cloudstack/blob/4.11/tools/docker/Dockerfile.centos6
from cloudstack
ers mailing list and the response
I got was that the usage server should be on by default in the docker
container. I got sidetracked by other things and am coming back to
this issue.
Is it meant to be running by default? or is there something needed to
do to turn it on
Ok, then it isn’t installed but that it can.
# yum install cloudstack-usageit makes sense to look at the docker definition
and do it there
On 12/07/17 09:07, "John McDonnell" <mcdonnell.j...@gmail.com> wrote:
Hi,
Any idea how to start it when running in the
maybe a double post due to mail issues:
Ok, then it isn’t installed but that it can.
# yum install cloudstack-usage
assuming centos as base. It makes sense to look at the docker
definition and do it there
On Wed, Jul 12, 2017 at 9:07 AM, John McDonnell
<mcdonnell.j...@gmail.com> wrote
Hi,
Any idea how to start it when running in the Docker simulator?
Obviously the service talked about here[1] isn’t available in the container, so
I can’t just 'service cloudstack-usage restart’.
[1]:
https://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/usage.html
esponse
> I got was that the usage server should be on by default in the docker
> container. I got sidetracked by other things and am coming back to
> this issue.
>
> Is it meant to be running by default? or is there something needed to
> do to turn it on in the container? (wasn't sure if this
Hi,
I asked this back in April on the Users mailing list and the response
I got was that the usage server should be on by default in the docker
container. I got sidetracked by other things and am coming back to
this issue.
Is it meant to be running by default? or is there something needed to
do
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1815
Thanks @rhtyd !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1815
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1815
I've not verified this but I'll proceed with merging this based on
review/test/feedback from @pdion891 @resmo and @sebgoa .
---
If your project is set up for it, you can reply to this email and
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1815
Thanks @rhtyd, let merge it so we have the simulator back online on docker
hub and let's improve our Docker images...
@jburwell, @rhtyd , do I merge it or you do it? I'm just wondering
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1815
Thanks, @pdion891 are you satisfied with the changes or you want to improve
them. I'm LGTM on this, can merge on your conclusion. Thanks.
---
If your project is set up for it, you can reply to
Github user resmo commented on the issue:
https://github.com/apache/cloudstack/pull/1815
IMHO this is not meant for production, but quick fire up a docker having
the current state of development. The image will be huge but for non-devs (like
me) a easy way to get a running devel
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1815
@sebgoa , I agree with you, it's just the easiest way to have a cloudstack
with simulator preconfigured ready to work. We should not use package for the
image management also.
I've
Github user sebgoa commented on the issue:
https://github.com/apache/cloudstack/pull/1815
LGTM
but really the database should be outside the mgt server container and we
should not be using supervisord.
---
If your project is set up for it, you can reply to this email and
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1815
@pdion891 @resmo @swill @sebgoa can you help review, test this? thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1815
@pdion891 thanks, how may I test this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user pdion891 opened a pull request:
https://github.com/apache/cloudstack/pull/1815
Fix docker image build for cloudstack-management
CLOUDSTACK-9651
Fix Docker images build for 4.10.0.0:
- simulator
- marvin
- management_centos6
You can merge
Github user pdion891 closed the pull request at:
https://github.com/apache/cloudstack/pull/1814
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user pdion891 opened a pull request:
https://github.com/apache/cloudstack/pull/1814
fix docker images build
CLOUDSTACK-9651;
Fix Docker images build for:
- cloudstack-simulator
- cloudstack-management
- marvin
Updated for version 4.10.0.0
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1548
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1548
merging this now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1672
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1672
LGTM merging now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1672
LGTM
Let's get this one in quickly. Doesn't touch any code or will break
anything.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user milamberspace opened a pull request:
https://github.com/apache/cloudstack/pull/1672
In comment, Add missing packages for Docker Ubuntu builds
Please note: No need to wait the results of Jenkins or Travis, this fix
only add the missing packages in the docker command
Github user moul commented on the issue:
https://github.com/apache/cloudstack/pull/1548
Rebased for Travis
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user bvbharatk commented on the issue:
https://github.com/apache/cloudstack/pull/1548
### ACS CI BVT Run
**Sumarry:**
Build Number 190
Hypervisor xenserver
NetworkType Advanced
Passed=72
Failed=1
Skipped=3
_Link to logs Folder (search
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1548
LGTM based code review. This is a very straight forward change.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
According to Wikipedia, OpenStack supports Docker but Cloudstack does not.
https://en.wikipedia.org/wiki/Docker_(software)
Can someone who knows the state of Docker support, add a word or two
about Cloudstack.
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack/pull/1548#issuecomment-221301992
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
spent enough time with Docker to give me the the
missing LGTM vote. Thanks...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user moul commented on the pull request:
https://github.com/apache/cloudstack/pull/1548#issuecomment-221256635
@swill, this solution is backward compatible, the `.dockerinit` file always
cohabited with `.dockerenv`, until recently, `.dockerinit` was removed while
`.dockerenv`
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1548#issuecomment-219793684
@moul can you post some verification that this fix works?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user wido commented on the pull request:
https://github.com/apache/cloudstack/pull/1548#issuecomment-219651953
LGTM
Very simple Docker fix
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user moul opened a pull request:
https://github.com/apache/cloudstack/pull/1548
Compabitility fix for Docker >= 1.11 (docker/docker#19490)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/moul/cloudstack patc
Thanks! That helps a lot.
Wido
> Op 30 april 2016 om 9:05 schreef Sebastien Goasguen <run...@gmail.com>:
>
>
> done
>
> > On Apr 30, 2016, at 8:58 AM, Wido den Hollander <w...@widodh.nl> wrote:
> >
> > Hi,
> >
> > I am working on
done
> On Apr 30, 2016, at 8:58 AM, Wido den Hollander <w...@widodh.nl> wrote:
>
> Hi,
>
> I am working on the Ubuntu 14.04 and 16.04 packaging. Using Docker I want to
> start building the packages for all distros.
>
> I'd like to publish the Docker
Hi,
I am working on the Ubuntu 14.04 and 16.04 packaging. Using Docker I want to
start building the packages for all distros.
I'd like to publish the Docker images to Docker Hub:
https://hub.docker.com/r/cloudstack/
Can somebody grant 'widodh' access to the registry?
Wido
1 - 100 of 150 matches
Mail list logo
